The Precedent handbook
Organise with Areas
Areas are flat tags for related decisions. Add as many as a decision needs, and find it through any of them.
Start with areas that fit your work
Setup is one page: name the workspace, choose its starting Areas, and create it. You need at least one Area to create the workspace. With one writable Area, the decision editor selects it for you.
On hosted Precedent, your first workspace starts on Free for one person, and you upgrade to Teams under Settings, Billing before inviting anyone.
Describe your work in a sentence or two and choose Suggest Areas. The suggested Areas join your list, where you can rename them, edit their descriptions, remove them or add your own. Undo reverses the last set of suggestions added, or the last Area removed. Your text is sent to the AI provider only when you choose Suggest Areas.
A preview beside the form shows the workspace and its Areas. Nothing is created until you choose Create workspace.
AI suggestions are limited to five per person per day, and setup shows how many are left. When none are left, or AI is unavailable, you add your Areas yourself.
Choose a useful grouping
A decision can belong to more than one area. Start with a few recognisable areas and add more as the record grows. Every decision needs at least one area before it can be approved. Each area also sets how many approvals its decisions need; see Approve decisions.
Create and use an area
- Open Areas and choose New area.
- Enter a name and describe what belongs there.
- Choose visibility and groups where your permissions allow it, then select Create area.
- Choose the area in the decision editor. To browse its records later, open it from Areas or follow an area chip on a decision.
To change an area, open it and select Edit area. On a phone, the area actions appear below its description and members; group roles and membership are edited in Settings, Groups. Update the fields and select Save changes.
Area creation and editing warn before you leave with unsaved changes. Choose Stay to keep your input or Discard changes to leave. Failed saves keep your input so you can correct it and try again.
Workspace administrators create areas. A linked Area administrator group can manage its areas, including visibility, linked groups and archive status. Members and Maintainers can edit metadata on areas assigned to their groups. Viewers cannot edit them.
Manage access with groups
Administrators is the only built-in group and gives full administration within its workspace. It cannot be renamed or deleted. The last administrator cannot be removed, including through direct calls.
In Settings → Groups, choose Viewer, Member, Maintainer or Area administrator for each custom group, then add users. Every member receives that group’s role on its linked areas. Select groups in Edit area; there is no separate area-role selector. Roles apply only on directly assigned areas.
Overlapping groups use the highest role: Area administrator, Maintainer, Member, then Viewer. A decision attached to several areas uses the highest applicable role across those areas. Whole-workspace visibility grants reading only. Without an applicable group, a person cannot write or approve. Administrators retain full access everywhere in their workspace.
Only the protected Administrators group grants workspace settings and group membership management. An ordinary Area administrator group applies to its linked areas. Existing mixed-role memberships are split into groups that preserve their permissions. Unlink a group from every Area before deleting it; its card in Settings → Groups lists those Areas, and Delete group stays turned off until none remain. Role changes and removals revoke affected assistant grants; permissions are checked on subsequent requests.
Tag decisions with multiple Areas
Select all relevant Areas in the decision editor. AR-041 choosing Postgres over Elasticsearch for Catalogue search could carry both Catalogue and Infrastructure tags. It appears under both Areas, subject to existing permissions.
Areas have no types, parents or inherited coverage. Existing decisions keep only their explicitly linked Areas. To make a decision apply in another Area, add that tag in the editor.
Area-bound assistant connections read decisions tagged with that Area. Shared decisions require a workspace connection to edit. Portals and channel notifications keep their explicit audiences.
Understand visibility before sharing
Whole workspace makes the area visible to workspace members. Restricted to groups limits the area to users in the selected groups and workspace administrators.
A draft with no areas is visible across the workspace; only Administrators can create or edit it until it has an assigned area. Workspace administrators can see all areas and decisions. Search, Ask AI, and assistant access use the same visibility rules.
Read an area's page
An area's page lists its decisions straight after the name and description, grouped as Expired, Reviews due, Decided, Upcoming, Drafts, and Superseded and reversed. Each row shows the owner and the full review text: the review date, how long ago it fell due, or the condition that opens the next review. For a Type that requires a date, it shows the expiry date instead. A decided decision whose proposed change waits for approval also shows the kind of change, such as Reversal proposed, and stays as decided until the change is approved.
People with Member, Maintainer or Area administrator access on the area, and workspace administrators, see New decision in followed by the area's name, which opens the editor with the area selected. The button is absent on an archived area. Viewers see the decisions only, even when they write in other areas.
The same people can expand For integrations at the bottom of the page. It holds the server URL (MCP) for an assistant connection limited to this area and the Area id to copy into a repository's .precedent.json for the pull request check. With Slack connected, Area administrators and workspace administrators also find the area's Slack channel settings there. An archived area takes no new assistant connections, so its page leaves out the server URL.
While a workspace is read-only, its areas' pages list decisions only. Creating, editing, archiving and the integration settings return once the workspace can be changed again.
When repositories follow the Area, the line above its name shows how many, and a Repositories section lists them after the decisions, with the folder pattern for a repository that follows it only through a folder.
Connect an area to a channel
With Slack connected, an area can name a channel for posts and review notices, under For integrations on the area's page. Captured decisions from that channel are filed under the linked area. An Area administrator or workspace administrator can also enable Suggest drafts from this channel; it is off by default.
Review the capture guide before enabling suggestions so you understand which conversations are read and how the workspace's model is used.