Organizations & Teams

Multi-org and multi-team structure, team members, invitations, and request-access workflows.

Organizations

An organization is the top-level administrative boundary. Org administrators manage teams within the org and can invite other org admins. Content itself is owned by teams, not directly by the org.

Organization administration

Org admins access administration from the dashboard or directly at:

  • Organizations list /app/d/orgs
  • Organization details /app/d/orgs/[orgId]
  • Organization administrators /app/d/orgs/[orgId]/org-administrators

When you provision via Get Started, you automatically become an org administrator for your new organization.

Inviting org administrators

  1. Go to Organization Administrators for the org.
  2. Click Add Administrator and enter the invitee's email, first name, and last name.
  3. The invitee sees a pending card on their dashboard under Organizations you administer.
  4. They click Accept Invitation, which calls POST /api/v1/d/orgs/[orgId]/accept-admin-invitation and activates their admin record.

Creating additional teams

Org administrators create teams from /app/d/orgs/[orgId]/t/new. The same provisioning cascade runs as initial Get Started setup (team, member, user groups, default app, project, environments, tokens, and Development defaults) — except the creating user is added as team member rather than going through the invitation-code flow again.

Teams

A team is where day-to-day content work happens. Each team has its own members, permission groups, widgets, collections, media library, and component library registry.

Open a team from your dashboard or navigate to /app/d/orgs/[orgId]/t/[teamId]. The team page shows projects and a members tab with links to team settings.

Team members

Viewing members

Team members are listed at …/team-members. Requires GET_TEAM_MEMBERS permission (via an appropriate user group).

Inviting a member by email

  1. Go to Team Members → Add Member (…/team-members/new).
  2. Enter email, first name, and optional last name.
  3. Submitting adds the person as a pending team member — status shows as Not joined yet until they are approved.

Joining a team after an invitation

After a team admin invites someone by email, that person must have (or create) a RuleCMS account using the same email address. To become an active member, they use the request access flow below. A team admin reviews and approves the request.

Request access (self-service join)

A signed-in user who is not yet a team member can request access from team settings.

  1. User submits a request via team settings (request access).
  2. A team admin with GET_TEAM_REQUESTS / PUT_TEAM_REQUEST opens …/team-requests.
  3. Admin approves the request. The member becomes active and can access the team according to their user groups.

Member detail and user groups

Each member has a detail page at …/team-members/[userId] where admins assign user group memberships. User groups control what the member can see and do on the member detail page above.

Multi-org, multi-team navigation

RoleWhat you see
Team memberTeams on the dashboard; direct links into team → project → environment workflows.
Org administratorOrg administration area to manage teams, org admins, and cross-team settings. Does not automatically grant team-level permissions unless also assigned user groups on that team.
Storage reminder: Images and component libraries belong to the team. Widgets, collections, and published content belong to a project environment within that team.