Permissions⚓︎
This document explains what each participation role is allowed to do inside a Topic. For identity boundaries, see Roles. For the technical permission keys and evaluation model, see Authorization Model.
Role Capabilities⚓︎
Permissions in DMS are tied to visible roles inside a Topic.
| Role | What this role can do |
|---|---|
| Owner | Create and manage the Topic, add Choices and Reasons, make the Decision, assign roles, record Outcomes, and write Lessons |
| Advisor | Add Choices, add Reasons, and contribute contextual notes |
| Reviewer | Record Reviews, write Lessons, and add contextual notes after the Outcome is known |
| Observer | View the Topic and follow its history without changing the record |
Capability Areas⚓︎
Topic Management⚓︎
- Owners can update Topic metadata, change roles, and close or reopen a Topic when appropriate.
- Advisors, Reviewers, and Observers can read the Topic if they have access, but they do not manage the Topic itself.
Choice and Reasoning⚓︎
- Owners and Advisors can add Choices and Reasons during consideration.
- Reviewers and Observers do not add decision options or reasoning.
Decision⚓︎
- Owners make the Decision and record the Expectation.
- Other roles may contribute input, but they do not make the final Decision.
Review and Learning⚓︎
- Owners and Reviewers can record Outcomes, Reviews, and Lessons.
- Advisors may continue to add contextual notes when allowed, but they do not own the review step.
Product Rules⚓︎
The permission model follows a few simple product rules:
- Participation is explicit: A person must hold a role in the Topic to act inside it.
- Authority is limited: Not every participant can make a Decision or change access.
- History is protected: No role can silently remove authored decision memory from the record.
- Visibility still applies: Permissions do not override scope, privacy, or sensitive-content rules.