Users
Users, organization membership, and actor context in DevDocs.
The user model represents a person acting inside DevDocs. Most product decisions should be made with the active organization in mind, because docs sites, releases, domains, and API references belong to a workspace rather than to an individual.
User context
A DevDocs request should resolve:
user_id- primary email
- active organization
- organization role
- allowed actions for the current resource
Organization membership
Organization membership controls who can review previews, promote releases, manage domains, and configure API playground execution.
| Membership state | Product behavior |
|---|---|
| Signed out | Public docs only |
| Signed in, no org | Show account state and guide the user to join or create an organization |
| Org member | Allow review and collaboration flows |
| Org admin | Allow production, domain, auth, and external execution controls |
Actor records
Audit events should store enough actor context to explain a decision later:
{
"actor": {
"user_id": "user_123",
"organization_id": "org_123",
"role": "org:admin"
},
"action": "release.promote",
"target": "rel_123"
}This same actor model should eventually appear in playground request history, domain changes, release approvals, and API reference imports.