Role based access control (RBAC) in Tines 3B provides a flexible, non-hierarchical approach to managing permissions. Unlike traditional structures, Tines 3B operates on a model of principles, scopes, and roles to ensure granular security across your tenant.
Core concepts
To effectively manage access, it helps to understand the three primary pillars of the RBAC system:
Principles: These define who is receiving access. This includes individual users and user groups. User groups allow you to bundle users together, making it easier to manage permissions for entire teams at once.
Scopes: These define where access is applied. In Tines 3B, a scope can be the entire tenant, specific spaces, connectors, or user groups.
Roles: These define what a principle can do. A role is a collection of permissions tied to a specific scope.
Learn how these all work together in Tines 3B here.
Setting up your environment
When you first join a tenant, you will need to organize your access structure.
Create user groups: Navigate to the "groups" list in settings. Organizing users into groups (e.g., Engineering, Security, HR) is the most efficient way to manage access.
Assign roles: You can assign tenant-level roles to these groups to determine their baseline capabilities, such as the ability to create new spaces, apps, or user groups.
Manage spaces: When creating a space, you define its Managers (who can invite others) and Editors (who can modify workflows). These roles can be assigned to either specific users or entire user groups.
Manage connectors: Access to connectors is managed explicitly. A user group may have access to a space, but they cannot use a connector within that space unless they are also specifically granted permission to use that app.
Example: If the "Engineering" group has edit access to a "DevOps" space, they cannot use the "GitHub" app in that space until the "Engineering" group is also granted edit access to the "GitHub" app.
Read how to set up your tenant in the right order here.