Getting Started: Groups & Permissions

Supported Plans

  • Basic
  • Pro
  • Premier

A group is a way to categorize people within an organization. Users may belong to one or many groups. Groups can be based on departments, roles, or location. Some examples: Sales Team, Senior Managers, Boston.

A role defines the level of access a user has to particular features and/or locations. Users may be assigned to one or many roles.

By default, all new users are assigned to the “member” role.  A user will always belong to the member role (this role cannot be removed), but new permissions can be added for that user by assigning another role. Additional roles can be custom roles or default roles ( admin, owner).

Basic and Pro plans have 3 default roles; member, admin, & owner. Learn more on default role permissions here

Premier plans can modify default roles or create new custom roles, and then assign members to those roles. This role based access control helps provide admins with a set of keys they can choose to distribute to their users.

 

Whether you’re using SCIM or not, we breakdown how to manage Groups and Permissions below:

Without SCIM

Offices without SCIM will manage their Groups and Permissions entirely inside Robin.

  1. Create Groups & Add Users
  2. Create Roles
  3. Add Permissions to Roles 

With SCIM

Offices with SCIM will need to configure Groups and Permissions inside Robin initially; but once you’re setup—the rest runs on auto-pilot and can be managed almost entirely from your Active Directory. 

  1. Create Roles
  2. Add Permissions to Role
  3. Configure Robin for SCIM
    1. Enabling the automatic provisioning/deprovisioning features within your Active Directory will allow Robin to constantly keep things in sync.
  4. Push Users and Groups to Robin
    1. Done within your Active Directory
  5. Connect Groups to the correct Roles
    1. See Step 1 Resource
Did this article help?