strataDocs

Team Collaboration

Strata is built for teams. Organizations group members and projects together, with role-based access control, plan tiers, and invitation-based onboarding.

Organizations

Organizations are the top-level container in Strata. Everything — projects, members, settings, billing, and SSO — belongs to an organization.

  • Each organization has a unique slug that forms its URL path (e.g. /acme-agency/projects/...)
  • A user can belong to multiple organizations, which is useful for freelancers or consultants working across agencies
  • Organization settings include name, logo, billing (Stripe integration), SSO configuration, and plan management

RBAC roles

Every organization member has exactly one role that determines their permissions. The role hierarchy is:

Owner > Admin > Member > Viewer

There is also a Guest role, but it is project-scoped rather than organization-scoped. See Project Guests for details.

Role descriptions

RoleDescription
OwnerFull control over the organization: billing, member management, SSO configuration, all project operations, and all admin/member permissions.
AdminCan manage projects and templates, review/reject/rollback changesets, manage project settings and registry, and perform all member-level operations.
MemberCan create and edit entries, commit changes, manage the project registry, and export. The standard contributor role.
ViewerRead-only access to all projects in the organization. Cannot make any changes.

Permissions matrix

Each role grants a specific set of permissions. Higher roles inherit all permissions from lower roles.

PermissionViewerMemberAdminOwner
entry:create / update / soft_delete
changeset:commit
changeset:review
changeset:reject
changeset:rollback
project:settings
project:registry
org:templates
export
org:members
org:settings
org:sso

Invitations

Strata uses an invite-only model. There are three ways a user can join:

  • Organization invitation — an Owner sends an email invitation specifying the role (owner, admin, member, or viewer). The recipient follows the link to create their account and join the org. Invitations have an expiration date and can be pending, accepted, rejected, or cancelled.
  • Claimed domain — if the org has claimed and verified an email domain (see SSO), users with that email domain can sign up directly. They still need to be added to the org by an admin or via JIT provisioning.
  • SSO / OIDC — users signing in through the org's identity provider are auto-provisioned as members.

Open self-registration is not available. Users who are not invited, do not have a claimed domain, and do not have SSO configured cannot create accounts.

Plan tiers

Organizations have a subscription plan that determines resource limits. Plans gate creation only, never access— an org that downgrades can still view and export all existing resources but cannot create new ones until they are back under the limit.

PlanProjectsMembersGuestsAI
Free132
Team101510
BusinessUnlimited5025
EnterpriseUnlimitedUnlimitedUnlimited

Limit details

  • Projects — total number of projects the org can create
  • Members — total organization members (across all roles)
  • Guests — total distinct guest users across all projects in the org (not per-project)
  • AI — AI-assisted content modeling (BYOK — bring your own API key). Available on Business and Enterprise plans.

Plan upgrades and downgrades are managed through the organization settings page with Stripe-powered billing.

Multiple organizations

A single user can belong to multiple organizations. This is common for:

  • Freelancers who work with multiple agencies
  • Consultants who need separate workspaces for each client
  • Developers who belong to both a personal org and a company org

The organizations dashboard shows all orgs you belong to. Each org has its own plan, members, projects, and settings — they are completely independent.