> For the complete documentation index, see [llms.txt](https://docs.allshore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allshore.ai/your-clients-portal-and-trust.md).

# Your clients' portal & trust

## The client portal

Your clients' contacts get their own portal — invite them from the client's detail page. Two roles: **client admin** (can approve and manage their own users) and **client viewer** (read-only). The portal contains exactly:

* **Approvals** — submitted timesheets awaiting their sign-off (their home page).
* **Roster** — who from your firm is engaged with them.
* **Compliance** — credential *status* of consultants engaged with them (labels and dates only).
* **Submissions** — candidates you've put forward.
* **Invoices** — with stable PDF downloads.
* **Contracts** — executed documents only (active/expired/terminated — never drafts or voided), with PDF download.
* **Users** — client admins manage their own portal users.

## What clients can never see

The portal is hard-fenced at the platform level — not hidden by UI, enforced on every read:

* pay rates, classifications, or anything about compensation
* your margins
* any other client's existence or data
* wellbeing data
* draft or voided paperwork

## How your data is protected

* **Tenant isolation.** Every record is fenced to your firm. Cross-tenant access fails closed and the isolation is covered by a dedicated test suite in continuous integration.
* **Append-only audit trail.** Every change — who, what, when — is recorded in the same transaction that makes it, and audit records can never be edited or deleted.
* **Field-level encryption.** Payout and banking details are encrypted (AES-256-GCM) with audited, admin-only reveals.
* **The back office has no standing inside your tenant.** Platform operators administer the tenant registry only; they cannot browse your data.
* **The platform never holds funds or files taxes.** It computes, exports, and records; money moves on your rails.
* SOC 2 Type II is the operating target: the controls above are CI-gated, not aspirational.

*Detailed pages (inviting contacts, portal walkthrough for your clients, security one-pager) are being added — tracked in Linear milestone **M30**.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.allshore.ai/your-clients-portal-and-trust.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.