Actors, Roles, and Permissions
Business roles
| Role | Product access | Responsibilities |
|---|---|---|
| Issuer | Issuer workspace | Encompasses fund managers and fund operations staff. Creates, configures, launches, services, and closes funds. Issuer is not the platform-wide Administrator. |
| Investor | One Torque investor experience | Discovers funds, completes eligibility, subscribes, funds, holds, receives distributions, and redeems through the connected public site and dashboard. |
| Administrator | Administration workspace | Accesses all funds and all issuers. Administers users, permissions, platform settings, records, and exceptions through the administration workspace and all admin-web functionality. Administrator is not the Issuer's fund manager and is not Operator. |
| Operator | Partner's own Torque-based platform within enterprise scope | Operates its own platform under an enterprise agreement. Operator is not a separate Torque application or permission model. |
Actors and supporting participants
| Actor | Product access | Responsibilities |
|---|---|---|
| Visitor | Public site | Browses published content and funds, contacts support, and starts sign-up or sign-in. |
| Authenticated investor | Investor dashboard for owned profiles | Manages profiles, completes eligibility actions, submits investments, views servicing information, and performs investor-owned wallet actions. |
| Profile party | Information associated with a trust or entity profile | Supplies or updates information where the profile workflow requests it. Profile-party authority is determined by the owning service. |
| Issuer fund manager or fund operations staff | Issuer workspace | Performs fund work within the assigned fund scope. The source system can label these users Owner, Admin, or Operations. |
| Auditor | Fund-manager surface | Has read-only fund access. Auditor is a permission label, not an operating role. |
| Platform operations or compliance | Administrative services | Reviews eligibility, legal, payment, and operational exceptions where the owning system permits it. |
Owner, Admin, Operations, and Auditor are fund-manager permission labels. They are separate from the Issuer, Investor, Administrator, and Operator roles.
Access Rules
- Dashboard routes require an authenticated session.
- Profile-scoped dashboard routes validate that the selected
profileIdbelongs to the current user before rendering profile data. - A user can operate more than one profile. Changing a selected profile must not expose data from an unowned profile.
- Accreditation upload is not presented when the selected profile is already approved or pending according to the dashboard route guard.
- Tahoe route authentication is not itself an authorization boundary. Tahoe documentation assigns
funds.read,subscriptions.write, andfunds.writepermissions to the fund-manager API.
Fund Manager Permission Matrix
Fund-manager permissions are:
| Role | Read fund | Accept subscription | Sign fund-owned operation | Fulfill deposit or redemption |
|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes |
| Admin | Yes | Yes | Yes | Yes |
| Operations | Yes | Yes | Yes | Yes |
| Auditor | Yes | No | No | No |
| Investor | Investor-facing fund information only | No | Investor-owned requests and claims only | Claims shares or proceeds only |
The server is responsible for enforcing these permissions. Client-side visibility and route access must not be treated as authorization proof.