Use the customer portal

This guide explains how customers complete portal work and how staff publish and manage the same records. Your available controls depend on your verified membership, reviewer capability, and project scope.

Accept an invitation and enter the workspace

Complete these steps from the recipient-specific invitation email:

1. Open the SABLE invitation link before it expires.
2. Set your initial password on the SABLE Auth callback page.
3. Continue to the exact customer workspace and destination from the invitation.
4. Sign in with the same email address for later visits.

If the invitation expired, ask an admin or lead to resend it. If you already accepted it but cannot sign in, ask them to send a password reset. Recovery also returns through the SABLE Auth callback and then opens the intended portal destination.

Switch between authorized workspaces

Customers with more than one membership can change workspaces from the selector in the portal header:

1. Open the workspace selector.
2. Choose an authorized customer workspace.
3. Confirm the customer name in the portal heading before acting.

The selector contains metadata for your memberships only. Changing the client query parameter does not grant access to another workspace.

Find work that needs attention

Open Overview to identify the next owner:

• Your actions contains review decisions and replies assigned to the customer
• Our team’s actions contains work assigned to the delivery team
• Waiting on others contains external dependencies

Open an item to view its exact record. What changed since your last visit compares published activity with your prior recorded visit. It does not infer unrecorded progress.

Create and reply to a request

Create a customer-visible request from Requests:

1. Select New request.
2. Choose a project, or choose the general workspace option when your role allows it.
3. Enter a title and the outcome, context, timing, links, and response expectations.
4. Select up to 10 files that should accompany the opening request.
5. Select Submit request and wait for the request and its attachment reply to finish.

The browser creates the request first, then uploads the selected files through the private attachment flow and publishes them on its opening thread. If attachment delivery fails after request creation, open that request and retry the preserved files from its reply form instead of creating a second request.

Reply from the request detail:

1. Enter reply text, select files, or provide both.
2. Wait for each selected file to become ready.
3. Select Send reply.

A reply may contain attachments without text. Each reply accepts up to 20 attachments. A request retains up to 50 nondeleted files. Supported files are PDF, PNG, JPEG, WebP, DOCX, and TXT, with a 10 MiB limit per file.

The browser preserves reply text and completed uploads after a network failure or stale update. Retry the saved submission to reuse the same idempotency key. If another participant changed the request, refresh the record and submit the preserved draft against the new revision.

Review a released deliverable version

Open Reviews, then choose the deliverable version shown in the list:

1. Read the version number, change summary, content, discussion, and due date.
2. Add a comment when you want to provide context without recording a decision.
3. If you are the designated reviewer, select Approve version or Request changes.
4. Enter a comment before requesting changes.

client_viewer members can comment but cannot approve or request changes. client_reviewer members have the explicit decision capability. A decision applies only to the displayed immutable version. If staff release a newer version while the review is open, SABLE rejects the stale decision and preserves your draft.

Follow the shared plan

Open Shared plan to review published delivery commitments:

1. Open a milestone to see its outcome, owner, target date, and status.
2. Review its commitments, commitment owners, and dates.
3. Follow Blocked by links to the related milestone.
4. Read the schedule note for the customer-visible timing implication.

Only staff with the plan-management capability see milestone edit controls. Customer members read the published plan.

Search and open shared resources

Use the workspace search from any portal view:

1. Enter a term from a title, published update, milestone, review, request, or customer-visible conversation.
2. Open the matching record or released source.
3. Select Clear search to return to the current view.

Resources contains released documents and meeting summaries. An Open button appears only when the released record has an approved HTTPS or same-origin link.

Ask SABLE about shared work

Ask a question from Overview:

1. Enter a question about a shared decision, milestone, request, update, or resource.
2. Select Ask SABLE.
3. Open the citations beneath the answer to inspect its sources.

Ask SABLE uses released workspace evidence and customer-visible request events. It excludes internal notes, unpublished work, raw transcripts, storage paths, and restricted source bodies. When the evidence does not support an answer, SABLE says so instead of supplying a source-free answer.

Manage notifications

Open the bell button to manage your inbox:

1. Open a notification to follow its exact portal link.
2. Mark one notification read, or mark every visible notification read.
3. Open Preferences.
4. Enable or disable activity email.
5. Choose immediate delivery, a daily digest, a weekly digest, or off.
6. Set your time zone and both quiet-hour values, or leave both values empty.
7. Choose request, review, milestone, and published-resource categories.
8. Select Save preferences.

In-app delivery stays enabled. Access messages remain required because they carry account lifecycle information. Preference updates use a revision, so a second browser cannot overwrite a newer saved choice silently.

Invite and recover customer access

Admins and leads manage access from the staff launcher:

1. Open Portal without a client query parameter.
2. Find the customer and select Invite customer.
3. Enter the named recipient, choose client_viewer or client_reviewer, and make an explicit activity-email choice.
4. Submit the invitation and confirm the returned delivery state.
5. Use Manage access to inspect active members and invitation state.

Use Resend invite for an active or expired unaccepted invitation. Use Send password reset for an accepted identity. Use Revoke access with a reason when the person should lose the membership. Revocation takes effect on the next API check even if the browser still holds an Auth token.

Delivery state is factual: delivered means Supabase Auth sent the message, pending means the existing-user access email entered the portal notification queue, and failed includes the provider or tracking error. Accepted or revoked invitations cannot be resent.

Configure customer tabs and automation

Admins and leads can customize what each customer sees in their workspace:

1. Open the customer workspace as staff.
2. Open the Prepare workspace tab → Customer tabs & automation.
3. Choose which tabs to show: This week, Overview, Shared plan, Reviews, Requests, and Resources.
4. Choose which tab the customer lands on.
5. Under Cards on This week, choose which cards the customer sees on This week: Weekly updates, Recent meetings, Files, and Needs you. All four are on by default.
6. Optionally enable Share meetings without approval. Without it, each meeting waits for a person to publish it. To share the recording link as well, also check Also include the recording link. It can be checked only while sharing without approval is on.
7. Optionally enable Draft a weekly wrap every Friday at 12:00 ET. Every weekly update is written as a Weekly wrap; there is no format to choose.
8. Select Save settings to apply the changes.

A customer with no saved settings sees Overview, Shared plan, Reviews, Requests, and Resources (not This week) and lands on Overview — exactly today's portal. Hiding a tab does not protect sensitive material—only released items ever reach the portal. When a tab is hidden, customer notifications for that category are skipped, including posts to the customer's shared Slack channel.

Add important links

Admins and leads can add, edit, reorder, and archive important links in the same Customer tabs & automation section:

1. In the Important links subsection, select Add link.
2. Enter a title, web address (https or http only), and optional note.
3. Use Move up and Move down to change the display order.
4. Use Remove to archive a link; archived links are kept but hidden and do not appear in the workspace.

Share meetings without approval

Enable this setting in Customer tabs & automation (see Configure customer tabs and automation above) to share eligible meetings automatically. SABLE shares the meeting title and SABLE's summary. SABLE itself never shows transcripts or internal meeting records in the portal.

The recording link is a separate choice, Also include the recording link, and is off by default. The link opens the provider's share page, for example Fathom, which may show the recording and its transcript depending on your Fathom sharing settings. When the link is included, meetings without a recording link are skipped; when it is off, they are shared with their title and summary. Applies to meetings shared from now on; meetings already shared keep their current setting.

Turning the setting on also shares eligible meetings from up to the backfill window before it was turned on (30 days by default). The attendee's domain must match a domain signal on that project (internal domains excluded). Meetings outside the backfill window are skipped, and nothing is released if the admin or lead who last saved these settings loses admin/lead access. See Understand the customer portal for the full qualification rules.

To stop sharing a specific meeting, either withdraw its publication or mark it Internal.

Prepare and publish workspace content

Admins and leads use the workspace preparation controls before inviting a customer:

1. Open the customer workspace as staff.
2. Open its publication inventory.
3. Filter by document, meeting, or draft, search by title, and verify the project shown on each row.
4. Open the bounded preview and resolve every listed blocker.
5. For a document or meeting, enter the customer-facing title and summary.
6. Choose whether to include the approved source link.
7. Publish the resource and confirm the shared count increases.
8. Publish a direct customer update when the customer needs a dated status message rather than a source resource.

Consultants can browse publication candidates within their active or current assigned projects. Only admins and leads can publish or withdraw them.

To withdraw an explicit share, open its publication detail, provide a reason, and submit the current publication revision. Withdrawal does not hide a document that remains linked from an active immutable released deliverable.

The inventory preview contains bounded metadata only. It does not expose document bodies or meeting transcripts. Publication stores the curated title, summary, and optional source link that customers receive.

Release approved work from Draft Workbench

Admins and leads publish deliverables from Draft Workbench:

1. Generate the draft and inspect the client body, internal evidence pack, and quality assurance report.
2. Resolve missing inputs and quality gate issues.
3. Approve the client body, with edits when needed.
4. Select Release to client after the draft status becomes approved and release-ready.
5. Open the portal and confirm the new version number, content, and customer visibility.

If the customer's Reviews tab is hidden, the release still completes and SABLE warns you that the customer can't see or approve it until Reviews is turned on in Customer tabs & automation.

Release-ready means the approved deliverable links to the selected draft, its quality gate is ready, and its QA issue and missing-input lists are empty. The release action creates an immutable version, revision-1 review state, release receipt, and notification events in one database transaction. An exact retry returns the prior receipt, while unchanged current content creates no duplicate version or email.

Approve and publish weekly updates

When auto-draft is enabled for a client, a weekly update draft is created automatically every Friday at 12:00 ET. The draft lands in Drafts as pending approval:

1. Open the Draft Workbench and find the pending weekly update.
2. Review the generated Weekly wrap: What we accomplished, What was surfaced, Next steps (owner-first, with client-owned items leading and Indigo's own items marked "(Indigo)"), and Meetings next week (scheduled portal touchpoints, with weekday and time).
3. Edit the client body as needed.
4. Select Approve & publish to client (or Approve edits & publish after making changes) to accept and publish the draft.
5. The update is now live in the customer workspace.

Use Copy as email to get a paste-ready subject line and message body if you want to send the update through email as well. This option is hidden on rejected or archived drafts. No separate release step is needed—approval is publishing for weekly updates.

Manage requests and private notes

Scoped staff can update a request from its detail:

1. Choose the assignee from people authorized for that client or exact project.
2. Set the status and next-response side.
3. Set or clear the response date.
4. Enter a resolution summary before selecting resolved.
5. Select Update request.

Use Internal team notes for staff-only context. Internal notes and internal attachments do not enter the customer thread, notification email, search results, or Ask SABLE evidence.

Publish a shared milestone

Admins, leads, and permitted project staff can maintain the shared plan:

1. Open Shared plan and select New milestone.
2. Choose the permitted project when the milestone is project-scoped.
3. Enter the title, outcome, status, target date, and accountable owner.
4. Add commitments with their status, owner, and due date.
5. Add a blocker and schedule note when they affect the published outcome.
6. Confirm customer visibility and save.

Each update requires the current revision and replaces the full commitments array. SABLE rejects stale writes and milestone dependency cycles.