Skip to content

The Precedent handbook

Workspace settings

Give people the right access, see how many approvals each Area needs, and choose how the team keeps its record. Some settings are available only to workspace administrators.

Settings groups its pages by task: Workspace (General, Portals); People and access (Users, Groups, Access and SSO); Governance (Approvals); Connections (Integrations, Assistants); Account (Data, Billing, Your preferences). Workspace administrators see every page; other people see the ones that apply to them. Older links to a Settings page keep working.

Invite people and assign groups

  1. As a workspace administrator, open Settings → Users.
  2. Select + Invite, enter the email address they will use to sign in and choose Viewer or Workspace administrator, then Send invitation. Precedent emails them an invitation. Add them to custom groups after they join.
  3. Ask them to sign in with that address. Their invitation is accepted when they sign in. Check Members for people who have joined and Pending invitations for people who have not. To cancel an invitation that has not been accepted, for example one sent to a mistyped address, choose Cancel on its row; this also frees any user licence it reserved.

A self-hosted deployment without email configured sends no invitation email. The dialog says so, its button reads Create invitation and it shows the workspace link to share; the person joins on first sign-in with the invited address.

On Free, which includes one person, the Invite button is replaced by Upgrade to Teams to invite people, which opens Billing. On Enterprise, while every user licence is used, the tab says beside Invite that a new person cannot be invited until a licence is free. On a read-only workspace Invite stays visible but turned off, and removing members and cancelling invitations still work.

For workspace administrators, the Members list shows each person as Workspace administrator or Group access, because their role on an area comes from their groups, with a group count. Expand the count to see every full group name and its role. Each group name links to its card in Settings → Groups. Other people see only the Workspace administrator or Group access label.

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 approving in every Area and changing how many approvals each Area needs. Keep at least one administrator. It never grants platform administration.

Each custom group has one role: Viewer, Member, Maintainer or Area administrator. Add users to one or more groups, then link a group to an Area from that Area's Edit area page. Each group card lists the Areas it is linked to, including archived ones, with a link to each Area's Edit page. Delete group stays turned off, with the reason shown, until the group is unlinked from every Area. For example, put a user in a Maintainer group linked to Area Y and a Viewer group linked to Area Z. The highest applicable role wins for overlapping groups or a decision attached to several areas. Access is evaluated independently for each Area.

RoleTypical responsibility
ViewerRead accessible decisions and search the record. Cannot create or approve decisions.
MemberCreate drafts and maintain decisions within their permissions. Can approve decisions in linked Areas, and ask for approval on decisions they own.
MaintainerCan reaffirm, supersede and reverse decisions they do not own in linked Areas.
Area administratorManage linked areas, their content, visibility, linked groups and how many approvals they need. Can ask for approval and dismiss a request for changes on decisions in those areas.
Workspace administratorManage the workspace, its settings, group membership and every area. Granted only by the protected Administrators group, which must keep at least one member.

Whole-workspace visibility grants reading. Writes require a linked Member, Maintainer or Area administrator group, except for Administrators. See area visibility and roles before changing access to sensitive records.

Approvals and decision Types

Each Area sets how many approvals a decision needs and whether its owner's own approval counts. An Area administrator or a workspace administrator changes them on the Area's form. Settings → Approvals lists every Area's rule and how many people have access, and marks a rule that cannot be met. See Approve decisions.

The same page holds Assistants can decide, which is on by default. When an administrator turns it off, no assistant connection in the workspace can decide, whatever permission it was approved with, and reading and drafting are unaffected. See Connect your AI assistant.

Precedent defines seven Types, and every decision has one. A decision's Type stays on it, appears in lists, and can be used to filter search and the export. An Exception always needs approval from someone other than its owner, whatever its Areas require, so a one-person workspace cannot decide an Exception until a second person has access. See The seven Types for what each Type needs before it can be approved.

Single sign-on

Workspace administrators set up single sign-on in Settings → Access and SSO under Enterprise SSO. The identity provider is configured on the server first: any OpenID Connect provider, or SAML through WorkOS. Choose the provider and the email domains that join automatically. For SAML, add the WorkOS connection id.

People who sign in through the provider with a matching email domain join the workspace with read access to whole-workspace areas. Add them to custom groups under Settings → Groups for anything more. Anyone else still needs an invitation. Turn on Require SSO for everyone except workspace administrators to make the provider the only way in for members outside the Administrators group, assistant connections included; administrators keep another way to sign in so a broken provider cannot lock the workspace. Members provisioned this way show via SSO in the Users list.

Control notifications

In Settings → Your preferences, choose whether to receive notices about drafts, approvals and reviews, reminders about review dates and exception expiry, and a weekly digest. Select Save preferences. Draft assignments, approval notices, dependency reviews and changes proposed to your decisions share the Drafts, approvals and reviews preference; approval notices come by Slack direct message when you linked Slack, and by email otherwise. Review-date reminders reach you by Slack direct message when you linked Slack, and by email otherwise. Weekly digests help you catch open items without repeatedly checking the inbox.

When an assistant connected as you approves, revises, reaffirms, supersedes, reverses, archives or reassigns a decision, you get a notice afterwards: which decisions, what changed, which assistant's app made the change and when. Changes within a working session share one notice, sent once ten minutes pass without another change, or thirty minutes after the first. It comes by Slack direct message when you linked Slack, and by email otherwise. No preference turns it off. Each change waited for a prompt in the assistant's app, but an app can be set to accept prompts without asking you, and Precedent cannot tell; this notice is how you find a change you did not accept. If you find one, review the decision and revoke the connection under Settings → Assistants. An approval from Slack that decides a draft, or a reaffirmation from Slack, sends the same notice, by email when Precedent can send email, because a direct message would go to the Slack account that made the change. If you did not make it, unlink your Slack account under Settings → Integrations. Changes you make in the web app, and drafts, evidence and links an assistant adds, send no such notice.

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 area channel setup.

Connect and revoke tools

Settings → Integrations holds workspace connections, including GitHub connections, Slack, your own model account, and evidence sources. A workspace administrator configures these. An individual assistant connection acts with the access of the person who authorised it.

Settings → Assistants shows one card per assistant name and person. Repeated authorisations are grouped under Manage connections, with the context, permissions, authorisation time, and activity of each connection. Revoke a connection when it should no longer access the workspace; other connections stay active. See Connect your AI 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 → General. The JSON export lists Precedent's Types, names each decision's Type and counts the decisions of each. Choose a Type beside Export to export only decisions of that Type, with their revisions, events, evidence and the links between them. The export log records which Type was exported. Every export, filtered by Type or not, includes the workspace's repository records and their history.

The signed audit export is under Audit export in Settings → Data. Choose a date range to download every decision event and assistant tool call in it, with the people and assistants named, plus exports and retention runs. The file is signed with the deployment's Ed25519 key over its exact bytes, so a reviewer can verify it offline against /.well-known/precedent-audit-key.json. Each export is itself logged. Keep the exported files together if you need to verify them later. See Compliance for how these records map to SOC 2 and ISO 27001.

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. Where billing is enabled, a workspace whose Paddle subscription will renew cannot be deleted until the subscription is cancelled; see Plans and billing. 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 area's decided history with portal users. Choose Grant access and enter their email address, then use Copy portal link to share the address yourself. Granting access sends no email; the person must sign in with the address you added. A portal is a separate reading experience and does not give those users general workspace access. An administrator can also choose Show governance report on a portal: the portal then shows the area's exception and review counts, read only, computed over the decided, superseded and reversed decisions the portal already lists. Drafts never count there, and approvals and requests for changes stay internal.

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, server URL (MCP) 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, Access and SSO, Approvals, Data, and Portals are workspace administrator settings. Billing appears only for workspace administrators 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 assistant calls stop. Use Plans and billing to understand trial expiry and restore a subscription.

Discard unsaved changes?

Your changes have not been saved. Stay to keep editing, or discard them and leave.