Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt

Use this file to discover all available pages before exploring further.

To grant a group of users permissions in Superblocks, you can either assign them an organization role that defines the Superblocks feature/admin permissions they receive, or a resource role that grant them access to an Application, Integration, Workflow, or Scheduled Job. To learn more about the types of roles and access they grant, see Permissions in Superblocks

​
Assigning org role to a group

To assign an organization role to a group:
  1. Click your avatar in the upper-left corner of the home page and click Organization Settings
  2. Click Groups
  3. Find the name of the group
  4. Click into the Role selector and choose the role you want to assign to the group
Assign custom role to user group

​
Removing org role from a group

To remove an organization role from a group:
  1. Click your avatar in the upper-left corner of the home page and click Organization Settings
  2. Click Groups
  3. Find the name of the group
  4. Click the × icon next to the role name

​
Managing a group’s access to a resource

Groups can be granted access to individual resources as well by assigning the group a resource role. To share a resource with a group:
  1. Navigate to the resource (Application, Workflow, Integration, etc) you want to grant access to
  2. Click into the editor or configuration page for that resource
  3. Find and click on the Share button in the upper right-hand corner of the page
  4. In the dialog box that appears, search for the group you want to share the resource with
  5. Select the Resource role you want to assign to the group
  6. Click Share
UI showing user assigning QA permissions to Product Teams for an Application

​
How group roles interact with individual member roles

Roles and permissions are additive. If a person is given different levels of access through different avenues, such as a group membership and their individually assigned role, the user has the sum of all access grants. For example, lets say an organization owner assigns a user the built-in role of End-User. They’re then added to a group that has a custom role with all Integrations permission. This member will have management access to all Integrations, but won’t be able to create Apps, Workflows, or Jobs, because of the permissions granted through the combination of their individually assigned role and the custom role. If a member belongs to multiple groups, the members permissions will include the permissions associated with the role individually assigned to them, plus the permissions granted to each of their groups.