docs: define organization account model
This commit is contained in:
@@ -11,9 +11,14 @@ These are cross-cutting rules for the current product and codebase. They are int
|
||||
|
||||
## Domain Constraints
|
||||
|
||||
- `Workspace` is the top-level scoping boundary.
|
||||
- An agency may manage multiple workspaces.
|
||||
- `Organization` is the SaaS account, billing, subscription, connector, and workspace ownership boundary.
|
||||
- `Workspace` is the brand/client workflow boundary.
|
||||
- A workspace belongs to exactly one organization and is not shared between organizations.
|
||||
- `ContentItem` belongs to a workspace scope.
|
||||
- Channels are configured inside a workspace.
|
||||
- Organization-level membership can grant inherited access to all workspaces owned by the organization.
|
||||
- Workspace-level membership can grant direct workspace access and override applicable inherited workspace permissions.
|
||||
- `External Collaborator` workspace participants can have workspace access without organization membership.
|
||||
- Comments, approvals, assets, and notifications must remain traceable to the underlying workflow entity they relate to.
|
||||
|
||||
## Backend Constraints
|
||||
|
||||
Reference in New Issue
Block a user