Skip to main content
Roles are used to define a set of permissions that you can assign to individuals or groups. Organization-level roles control the Superblocks features members can access, the administrative actions they can perform, and the level of access users have to all current and future resources created in the org. Note, organization-level roles differ from resource-level roles that give users access to specific Applications, Integrations, Workflows, etc. For more information, see About resource roles.

​
Built-in organization roles

Each Superblocks organization, by default comes out of the box with the following built-in roles. These roles are non-editable and are based on common patterns of permissions organizations usually need.
  • Owner: Each Superblocks organization has a primary Owner. This person is considered the controller of all org data. Only they can request to delete users, delete the organization, or request plan and billing changes.
  • Admin: Admins help manage their organization, including members, groups, and settings. Admins can also access all of the organization’s resources to help manage access to these resources.
  • Developer: The default non-administrative role is Developer. Developers build and maintain your company’s tooling. They can’t change org settings, but otherwise have read-only access to most of your org’s settings.
  • End-User: End-Users have the lowest level of access in Superblocks. They have read-only access to the platform, can’t view most org settings, and can only access resources they’ve been given access to.
For more granular control of permissions, you can create custom organization roles. For more information, see Custom organization roles For more information using roles, see Using organization roles

​
Permissions for built-in organization roles

The built-in organization roles have the following permissions. For a full list of permissions that can be assigned with organization roles, see the permissions reference