Organizations
Organizations are the top-level container on Dreadnode. Everything — users, workspaces, projects, credits, and billing — is scoped to an organization.
What an organization is
Section titled “What an organization is”An organization represents a team, company, or group that shares access to the platform. Each organization has:
- A unique
key(URL slug) used in API paths and URLs - A display
name - A member list with role-based access
- Workspaces that contain projects
Membership and roles
Section titled “Membership and roles”Users are added to an organization as members. Each member has a role that determines their permissions:
| Role | What they can do |
|---|---|
| Owner | Full access — manage members, workspaces, billing, keys |
| Contributor | Create and manage workspaces and projects |
| Reader | View workspaces, projects, and traces |
Invitations
Section titled “Invitations”Organization owners can invite users by email. Invitations have an expiration window and can be accepted or rejected by the recipient. External invites can be toggled on or off per organization.
Organization limits
Section titled “Organization limits”Each organization has a configurable maximum member count (default: 500). Platform administrators can adjust this limit.
Managing organizations
Section titled “Managing organizations”- API: Organization details are available at
GET /api/v1/org/{org}. Members are listed atGET /api/v1/org/{org}/members. - Workspaces: Listed at
GET /api/v1/org/{org}/ws.
Relationship to other concepts
Section titled “Relationship to other concepts”Organization ├── Members (users with roles) ├── Invitations (pending) ├── Workspaces │ ├── Projects │ │ ├── Sandboxes │ │ ├── Sessions │ │ └── Traces │ └── Permissions (user + team) └── Credits (SaaS mode)