Guides

Teams & Roles

Organizations let you collaborate on models with your team. Models created under an organization are accessible to all members.

Create an organization

Click the workspace switcher in the top-left of the app header. Choose Create organization, give it a name, and confirm.

You'll be the owner of the new organization.

Invite members

Open Organization settings from the workspace switcher. Go to the Members tab and click Invite. Enter the invitee's email address and choose their role.

Invitations expire after 48 hours. The invitee receives an email with an accept link. Pending invitations are tracked under the Invitations tab (admins only).

Roles

RoleView modelsEdit modelsPublish modelsManage members
Owner
Admin
Member
Commenter

Admin

Full access. Admins can invite and remove members, change roles, and create, edit, and publish models — everything except deleting the team (owner only).

Member

Can create and edit models — add entity types, relationships, and properties — but cannot publish a model to the public API. Publishing requires Admin or Owner.

Commenter role

Commenters can view all models in the organization and leave comments in the workbench, but cannot create, edit, delete, or publish anything. Ideal for product managers, designers, and external reviewers.

Team settings tabs

The organization settings page is divided into tabs:

  • Members — view the full member list, change roles, remove members, or invite new ones.
  • Invitations — manage pending invitations (admin only).
  • General — rename the team (admin only).
  • Danger Zone — permanently delete the team (owner only).

Click the icon next to any role selector to see a summary of what each role can do.

Remove a member

From Organization settings → Members, click the trash icon next to a member and confirm. Removed members immediately lose access to all org models.

Owners cannot be removed without first transferring ownership.

Switch workspaces

Use the workspace switcher in the top-left to toggle between personal and organization workspaces. Models and API keys are scoped to the active workspace.

API keys and organizations

API keys are account-scoped, not organization-scoped. A key inherits all the permissions of its owner — personal models and org models for every org the owner belongs to.