Skip to content

Roles & Permissions

Futurity uses role-based access control (RBAC) to manage what you can do within your organization.

  1. Permissions define specific actions (e.g., “create workflows”)
  2. Roles group permissions together (e.g., “Editor” role)
  3. You are assigned roles
  4. You can do what your role permits
Organization Owner
Administrators
Custom Roles
Members

The organization creator. Has all permissions and cannot be removed.

  • Full access to everything
  • Can transfer ownership
  • Cannot be suspended or removed

Full administrative access:

  • Manage users and roles
  • Access all organization settings
  • View all content
  • Full feature access

Standard user access:

  • Use Corint
  • Access Vault (owned and shared files)
  • Create and run workflows
  • View assigned dashboards

Read-only access:

  • View shared content
  • Cannot create or edit
  • Cannot access sensitive settings
PermissionDescription
corint:accessUse Corint AI assistant
corint:create_agentsCreate custom agents
corint:manage_agentsEdit/delete any agent
PermissionDescription
vault:accessAccess Vault feature
vault:uploadUpload files
vault:shareShare files with others
vault:deleteDelete files
vault:manageManage all organization files
PermissionDescription
workflows:accessView workflows
workflows:createCreate new workflows
workflows:editEdit existing workflows
workflows:deleteDelete workflows
workflows:activateTurn workflows on/off
workflows:manageManage all organization workflows
PermissionDescription
dashboards:accessView dashboards
dashboards:createCreate dashboards
dashboards:editEdit dashboards
dashboards:deleteDelete dashboards
dashboards:manageManage all organization dashboards
PermissionDescription
integrations:accessUse connected integrations
integrations:manageConnect/disconnect integrations
PermissionDescription
org:view_settingsView organization settings
org:edit_settingsModify organization settings
org:manage_usersAdd/remove users
org:manage_rolesCreate/edit roles
org:billingAccess billing settings
  1. Navigate to Role Editor

    Go to Organization → Role Editor

  2. Create New Role

    Click + New Role

  3. Name the Role

    Give it a descriptive name (e.g., “Marketing Team”)

  4. Select Permissions

    Check the permissions this role should have

  5. Save Role

    Click Save

Content Creator

  • corint:access
  • corint:create_agents
  • vault:access
  • vault:upload
  • vault:share

Workflow Administrator

  • workflows:access
  • workflows:create
  • workflows:edit
  • workflows:activate
  • workflows:manage

External Collaborator

  • vault:access (limited to shared folders)
  • dashboards:access
  1. Go to Organization → Role Editor
  2. Select the role to edit
  3. Modify permissions
  4. Click Save
  1. Select the role
  2. Click Delete
  3. Assign affected users to a different role
  4. Confirm deletion

Create a new role based on an existing one:

  1. Select the role to copy
  2. Click Duplicate
  3. Rename and modify as needed
  4. Save the new role
  1. Go to User Management
  2. Click on the user
  3. Click Edit Role
  4. Select the new role
  5. Save
  1. Select multiple users (checkbox)
  2. Click Bulk Actions
  3. Select Change Role
  4. Choose the role
  5. Apply

Some permissions imply others:

  • manage permissions include view/edit/delete
  • org:manage_roles requires org:view_settings
  • Admin role bypasses most permission checks
  1. Principle of least privilege: Give minimum necessary access
  2. Use roles, not individual permissions: Easier to manage
  3. Regular audits: Review who has what access
  4. Document custom roles: Keep records of what each role is for
  5. Test before deploying: Verify roles work as expected
  1. Check your assigned role
  2. Verify your role has the required permission
  3. Check if feature requires additional permissions
  4. Clear cache and retry
  1. Check all assigned roles (you can have multiple)
  2. Verify permission inheritance
  3. Check for admin role
  1. Verify you have org:manage_roles permission
  2. Check if you’re trying to edit built-in roles (some are locked)
  3. Organization owner can always edit roles