An Organization is the company umbrella above workspaces. It is meant for large teams that need one Enterprise contract, a shared seat pool, SSO/policies, and several product workspaces.
Solo users and small groups stay on workspace Free/Pro — see Workspaces. You do not need an Organization for that.
When to use an Organization
Use an Organization when you need:
- one Enterprise subscription covering many workspaces;
- a seat pool for people across teams;
- SSO and email-domain policies;
- an org-wide audit of admin actions;
- cross-team project sharing inside the company.
Create and open
- On the home screen open Organizations.
- Create an organization (you become
org_owner). - Open Organization admin (
/org/<slug>/admin). - Create workspaces under the organization and invite members.
Enterprise is assigned by DDDesigner sales / platform admin (not self-serve card checkout). Contact info@dddesigner.com.
Organization admin portal
Available to org_owner and org_admin:
| Section | Purpose |
|---|---|
| Overview | Seats used/total, workspace count, SSO status, contract end |
| Workspaces | Create and list workspaces under the org |
| People | Directory, roles, deactivate; seat meter |
| Teams | Catalog of teams across workspaces |
| Access policies | SSO flags, allowed email domains, share-link and guest policy |
| Billing & contract | Enterprise status (read-only; edits by platform) |
| Audit | Org actions with CSV export |
Roles
| Level | Roles |
|---|---|
| Organization | org_owner, org_admin, member, guest |
| Workspace | Workspace admin (org_admin in the API), team lead, architect, developer, viewer |
| Project | Architect, developer, viewer |
Organization admins use the org portal and can switch into any workspace of the company. Day-to-day modeling still uses project roles in Tools → People.
Seats and billing
- Enterprise seats are counted for active organization members (including guests).
- When a workspace is linked to an Organization with active Enterprise, its billing badge shows Covered by Organization.
- Pro self-serve checkout is blocked for covered workspaces.
Inter-team collaboration
Inside an Organization / workspace you can:
- set project visibility to team, workspace, organization, or restricted;
- grant another team viewer or developer access to a project;
- filter the project list by my team, all workspace, or shared with me.
Deeper cross-project Context Map stubs and Shared Kernel workflows are planned as follow-ups; access and grants are available now.
Policies
In Access policies org admins can:
- enable / require SSO (IdP metadata for OIDC or SAML);
- whitelist allowed email domains;
- disallow public share links;
- allow or deny guests (emails outside the domain list).
Next steps
- Workspaces — projects, invites, Personal Free/Pro
- Modeling — Context Map and Aggregates
- Working with AI — agent keys and project knowledge