Roles & Permissions

Created by Reachware Support, Modified on Sun, 15 Mar at 10:43 AM by Reachware Support

Keeping your data secure while your team works is a top priority. Reachware Studio uses Role-Based Access Control (RBAC) to help you manage who can see and do what in your account. Think of it as giving each team member the right set of keys for their specific job, no more, no less.

What is Role-Based Access Control (RBAC)?

RBAC is a security approach where permissions are assigned to roles, and users are assigned to roles. Instead of managing permissions for each individual user, you assign users to predefined or custom roles that come with a set of permissions.

Why Roles Matter

Instead of setting permissions for every individual user, you simply assign them a role. Each role comes with a predefined set of permissions based on job responsibilities. This approach:

  • Reduces complexity
  • Ensures consistent access control
  • Protects sensitive settings such as billing and subscriptions

How It Works in Reachware Studio

  • Define Roles: Use predefined roles or create custom roles
  • Assign Permissions to Roles: Each role has specific permissions (e.g., view flows, create users)
  • Assign Users to Roles: Add team members and assign them appropriate roles
  • Automatic Inheritance: Users automatically inherit all permissions from their assigned role

Reachware Studio Role Hierarchy

Reachware Studio follows a multi-level structure designed to support integration partners serving multiple client organizations:

  • Platform Level: Reachware Studio (Platform Owner)
  • Partner Level: Partners manage multiple client organizations
  • Organization Level: Organizations contain users and integrations

Each level has its own roles and permissions.

Role Types

Every role in Reachware Studio has a Role Type that defines where it applies.

Partner Role

Applies at the Partner user level. Used by integration partners managing multiple organizations.

  • Partner Super Admin (Highest)
  • Full Partner
  • Custom Partner Roles

Organization Role

Applies at the Organization user level. Used inside a specific organization. Permissions are limited to that organization only.

  • Organization Super Admin (Highest)
  • Organization Admin
  • Custom Organization Roles

A role cannot belong to both types (Partner/Organization). When creating a custom role, you must choose the appropriate role type.

Predefined Roles

Reachware Studio provides predefined roles that cannot be modified or deleted.

RoleTypeDescription
Partner Super AdminPartnerFull partner-level control
Organization Super AdminOrganizationFull organization-level control

Permissions Matrix

When creating or editing a role, permissions are assigned using the permissions matrix to define specific actions for each module.

Permission ModuleScope
UsersBoth
RolesBoth
OrganizationsPartner Only
SystemsPartner Only
OperationsPartner Only
ConnectionsBoth
Data HubsBoth
Flows TemplatePartner Only
Flows AssignmentPartner Only
FlowsOrganization Only

Available permissions for any module: List All, View Details, Create, Edit, Deactivate.

How to Create a Custom Role

To manage roles and permissions in a more flexible way, Reachware Studio allows partners and organizations to create custom roles.

1
Navigate to Roles

Go to Partner / Organization → Roles and Permissions.

2
Click Create Role
3
Fill in Role Details
  • Role Name: Must be unique
  • Role Description: Briefly describe the role's purpose
  • Status: Select Active or Inactive
4
Assign Permissions

Select the required permissions from the Permissions Matrix.

5
Save

Click Save to create the role.


Who Can Manage Whom

Partner Super Admin

Can ManageInviteEditDeactivate
Partner Super Admin
Organization Super Admin
Custom Partner Roles

Organization Super Admin

Can ManageInviteEditDeactivate
Organization Super Admin
Custom Organization Roles

Related Topics

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article