User Roles and Permissions

Ensuring that the right person has access to the right data and tools in Insycle is simple.

First, navigate to the Settings > Users page in the main navigation menu. There, you can individually select Insycle users and set their Insycle permissions on a module-by-module level.

Insycle's permissions serve as an additional layer of permissions on top of your in-app permissions. Any read or write access granted by Insycle permissions does not override the settings in your integrated CRM.

Once a team member has been invited to join your Insycle account, you can grant them permissions by assigning Read or Write access for each module or app. In order to modify data in a module or app, a user must have Write permission for that module. See our Module Overviews for information about the different modules.

To configure permissions for a user, open the Settings > Users page and click the checkbox by their name.

Next, assign permissions on a module-by-module basis.

Here are the sample permission settings for a user: Skyler can review duplicates and generate duplicate reports but cannot merge them. Additionally, Skyler will be able to import CSV files using Magical Import and collaborate with the team on corrections through Grid Edit. The remaining modules will not be visible to Skyler.

Read permission makes a module accessible and visible from the main menu. Without the Read permission, the relevant module will be hidden from that user. For example, the following user has Read access to the Merge Duplicates, Magical Import, and Grid Edit modules.

With Read permission, users can review data and templates, and run operations in Preview mode. However, users with Read but not Write permission cannot modify any data. This is ideal when you want users to test solutions and templates in Insycle but do not want them to modify data.

Write permissions allow users to save templates, execute operations in Update mode, and schedule automations. To modify any data, a user must have Write permission in the modules and apps.

A person can be assigned one of the following roles:

• Owner: An Owner can assign Admin roles and set permissions for other users. Only one user can have the Owner role in each Insycle account. This is typically the user responsible for bill payment.
• Admin: An Admin can set permissions for other users. Multiple users can have the Admin role.
• User: A User can perform read or write operations based on the permissions assigned to them by an Owner or Admin.
• Assignee: When team members are invited to join Insycle but have yet to log in, the Assignee role will appear. Once they log in, this will automatically change to the role they were granted.

Insycle's permissions serve as an extra layer of controls on top of your app's existing permission settings.

For example, if you don't have permission to edit records in HubSpot, you cannot edit records in Insycle regardless of your Insycle permissions settings. Insycle's permissions will never override existing permissions in your connected CRM.

When permissions are changed, they take effect immediately. Users do not need to log out and log back in; permissions are enforced right away. The visual menu changes will be visible on the next user login, even if the user can still see the menu items and editing options.

For example, if an admin removes Skyler's Write permissions from the Grid Edit module, from that moment on, Skyler will not be able to edit any data in Grid Edit.

Even if Skyler hasn't logged out and back in after the permissions change, they still won't be able to write data. If they attempt to modify data, they'll receive the following error message:

Permissions not assigned to user. Check permissions in Settings > Users.

After logging out and back in, the Edit options will not be available to Skyler, and similarly, saving Schedules or Templates will be disabled in the module settings menu.

Additionally, the Update mode in the Review dialog will also be disabled.

In order to run a Recipe, you need to have Write permissions for all the modules. Even if the target recipe doesn't use all modules, Insycle requires that in order to save or run a recipe, the user must have Write permissions for all the modules.