docs: define organization account model

This commit is contained in:
2026-05-04 15:45:12 -04:00
parent 9bdef978bd
commit cd6f402d9e
15 changed files with 555 additions and 21 deletions

View File

@@ -2,28 +2,67 @@
Use these terms consistently in product docs, specs, UI copy, and code discussions.
## Workspace
## Organization
Top-level working container for a client account.
SaaS account boundary that owns billing, subscription, limits, organization-level users, connectors, data mappings, and workspaces.
An agency may manage multiple workspaces.
An organization may be an agency, an in-house brand company, or a professional's business account.
Use:
- ownership boundary
- membership boundary
- scoping boundary for content items, assets, comments, approvals, and notifications
- billing and subscription boundary
- ownership boundary for workspaces
- connector and integration configuration boundary
- organization-level membership and permission boundary
Do not use as:
- synonym for a brand workspace
- synonym for a single human user account
- synonym for an external reviewer
## Workspace
Brand, client, or operating workspace where content workflow happens.
Each workspace belongs to exactly one organization and is not shared between organizations.
Use:
- brand/client workflow boundary
- scoping boundary for content items, assets, comments, approvals, and notifications
- channel configuration boundary
Do not use as:
- top-level SaaS account boundary
- billing or subscription boundary
- synonym for internal role
- synonym for team member role
## Organization Member
User access relationship at the organization level.
Organization membership can grant organization-level permissions and inherited access to all workspaces owned by that organization.
## Workspace Member
User access relationship at the workspace level.
Workspace membership grants direct access to one workspace and can classify the user's relationship to the owning organization as `Organization Member` or `External Collaborator`.
An `Organization Member` is part of the organization that owns the workspace. They may have access through organization membership, direct workspace membership, or both.
An `External Collaborator` is not part of the owning organization but has direct workspace access. This includes subcontractors, providers, clients, and external reviewers.
Workspace membership can override applicable inherited workspace permissions.
## Agency
Operating organization managing one or more workspaces.
Type of organization that manages one or more brand/client workspaces for customers.
An agency is above the workspace level in the business model.
Use `Organization` for the product model unless specifically describing an agency customer.
## Client
@@ -106,6 +145,8 @@ Examples:
Specific destination, account, handle, page, or feed within a network.
Channels are configured inside a workspace. The connector or integration credentials used to access external systems are owned by the organization.
Examples:
- `@MyBrand` on Instagram

View File

@@ -8,7 +8,7 @@ Active
`Socialize` is a workflow application for social media content review, revision, approval, and publication readiness.
It is not a public social network. It is a workspace-based coordination tool for internal teams, providers, and client approvers.
It is not a public social network. It is an organization-owned, workspace-based coordination tool for internal teams, providers, and client approvers.
## Problem
@@ -38,8 +38,11 @@ Provide one system of workflow for drafting, revising, reviewing, approving, and
## Core Product Shape
- workspace-based account boundary
- agencies able to manage multiple workspaces
- organizations as the SaaS account, billing, subscription, and connector boundary
- workspaces as brand/client workflow boundaries owned by one organization
- agencies, in-house teams, and professional businesses able to manage multiple workspaces
- organization members able to inherit access across owned workspaces
- external collaborators able to access specific workspaces without organization membership
- content items as the main reviewable unit
- assets and revisions tracked against content items
- comments and approvals attached to the work itself
@@ -60,7 +63,7 @@ Provide one system of workflow for drafting, revising, reviewing, approving, and
- not a full publishing engine in version 1
- not a full DAM platform in version 1
- not a full analytics product in version 1
- not a billing/subscription product in version 1
- not a full billing provider or pricing/package automation product in version 1
## MVP Scope
@@ -86,7 +89,7 @@ Version 1 should focus on approval workflow rather than direct publishing.
- direct social publishing
- advanced third-party synchronization
- analytics suite
- customer billing flows
- full customer billing provider integration and pricing/package automation
## Current Strategic Assumptions