Project Users & RBAC

Manage your team with role-based access control. Invite collaborators, assign roles, and control who can access and modify your content.

What is Role-Based Access Control?

Role-Based Access Control (RBAC) allows you to manage permissions by assigning roles to team members. Each role has specific permissions that determine what actions users can perform in your project.

This ensures that team members only have access to the features and content they need, improving security and workflow organization.

Available Roles

Owner

Full access to all project features including billing, settings, and user management.

  • Manage all content and settings
  • Invite and remove team members
  • Modify project configuration
  • Access billing and subscription
  • Delete the project

Admin

Manage content types, content, and most project settings (except billing).

  • Create and modify content types
  • Manage all content entries
  • Invite team members
  • Configure project settings
  • Cannot access billing or delete project

Editor

Create, edit, and publish content without modifying content types or settings.

  • Create and edit content entries
  • Publish and unpublish content
  • Upload and manage media
  • Cannot modify content types
  • Cannot access project settings

Viewer

Read-only access to view content and project structure.

  • View all content entries
  • View content types and structure
  • Cannot create or edit content
  • Cannot modify any settings

Inviting Team Members

Step 1: Navigate to Team Settings

Go to Project Settings and select the "Team" tab.

Step 2: Send Invitation

Click "Invite Member", enter their email address, and select a role.

Step 3: User Accepts Invitation

The invited user will receive an email with a link to accept the invitation and join your project.

Best Practices

  • Follow the principle of least privilege - give users only the access they need
  • Regularly review team members and their roles
  • Remove access for team members who no longer need it
  • Use the Viewer role for stakeholders who need visibility but not editing rights
  • Limit Owner and Admin roles to trusted team members
  • Document your team's role assignments and responsibilities