The Precedent handbook
Workspace settings
Give people the right access, set the confirmation policy, and choose how the team keeps its record. Some settings are available only to admins.
Invite people and assign groups
- As a workspace admin, open Settings → Users.
- Invite a teammate using the email address they will use to sign in and choose reader access or Administrators. Add them to custom groups after they join.
- Ask them to sign in with that address. Their invitation is accepted when they sign in. Check the Users list to see members and pending invitations.
Manage permissions in Settings → Groups. Administrators is the only built-in group. It cannot be renamed or deleted and gives full administration within this workspace, including confirmation under either policy. Keep at least one administrator. It never grants platform administration.
Each custom group has one role: Viewer, Member, Approver or Admin. Add users to one or more groups and link each node to one or more groups. For example, put a user in an Approver group linked to Node Y and a Viewer group linked to Node Z. The highest applicable role wins for overlapping groups or a decision attached to several nodes. Parent access does not inherit to children.
| Role | Typical responsibility |
|---|---|
| Viewer | Read accessible decisions and search the record. Cannot create or confirm decisions. |
| Member | Create drafts and maintain decisions within their permissions. Can confirm their own decisions under the default owner policy. |
| Approver | Confirm and steer decisions on nodes assigned to their group, including when approver sign-off is required. |
| Admin | Manage linked nodes, their content, visibility and linked groups. Confirm under either policy on those nodes. |
| Administrators group | Manage the workspace, its settings, group membership and every node. This protected group must keep at least one member. |
Whole-workspace visibility grants reading. Writes require a linked Member, Approver or Admin group, except for Administrators. See node visibility and roles before changing access to sensitive records.
Set confirmation policy and templates
Workspace administrators choose the confirmation policy in Settings → Security. The default allows the owner or an approver to confirm. Approver sign-off requires an Approver or Admin on an assigned node, or a workspace administrator.
Use Settings → Templates to view the available decision templates. Workspace administrators can manage templates, select extra required fields, and set a default review interval. Templates appear under Start from on the New decision page.
Control notifications
In Settings → Notifications, choose whether to receive draft assignments and dependency reviews, and whether to receive a weekly digest. Select Save preferences. Draft assignments and dependency reviews share a preference. Weekly digests help you catch open items without repeatedly checking the inbox.
The notification log shows delivery attempts. If a message is missing, check your preferences, the destination, and its delivery status. Slack notices also depend on the workspace integration and node channel setup.
Connect and revoke tools
Settings → Integrations holds workspace connections, including Slack, your own model account, and evidence sources. An admin configures these. An individual assistant connection acts with the access of the person who authorized it.
The Agents section in Settings shows one card per assistant name and person. Repeated authorizations are grouped under Manage connections, with the context, permissions, authorization time, and activity of each connection. Revoke a connection when it should no longer access the workspace; other connections stay active. See Connect your assistant for setup and troubleshooting.
Connecting an evidence source does not change permissions in that external system. Teammates may need access there to read the original material.
Export and manage retained data
Workspace administrators can export workspace data from Settings. The signed audit export includes a manifest and verification material alongside the recorded activity. Keep the exported files together if you need to verify them later.
Settings → Data controls retention and legal hold. Review the retention preview before running a purge: an archive removes a record from active lists, while a retention purge can remove eligible archived data. Legal hold prevents eligible data from being purged while the hold is in place.
Deleting a workspace removes its database records before removing uploaded evidence files. File cleanup that fails stays queued for the daily retention job to retry. Retention purges use the same cleanup queue.
Workspace administrators can use Settings → Portals to share a limited view of one node's decided history with invited portal users. A portal is a separate reading experience and does not give those users general workspace access.
Run your own deployment
The repository includes a local stack with demo data. From a checkout, run:
docker compose up --build
The README covers deployment configuration, environment variables, and database setup. Use documentation, MCP URL and skill download from your own deployment when connecting tools.
If a setting or action is missing
First check that you are in the intended workspace and have the right role. Groups, Security, Data, and Portals are admin settings. Billing appears only for admins on deployments with billing configured. Available sign-in and integration options also depend on deployment configuration.
If the workspace is read-only, reading and search continue, but most writes and all MCP calls stop. Use Plans and billing to understand trial expiry and restore a subscription.