CRM functions optimally by sharing as much data as possible within your organisation. However, sometimes it is necessary to shield data or restrict editing rights for a group of employees. By using roles within Tribe CRM, you can tailor the appropriate authorisation levels to your organisation's needs.
​

First, you should know that within Tribe CRM we have two types of users by default. The administrator and the 'normal' user. The administrator has access to all settings in the configuration and account settings. The user cannot access these functionalities, but has default rights to use all other functions within Tribe CRM. It is possible to give an employee administrator rights, just follow the steps below:
​

Before we dive straight into the roles, let us give you some background information on the structure of Tribe CRM. You will need this information when you start setting rights at field level.
​

In Tribe, we use different relationship types and activity types. Each relationship or activity type has its own fields, the specific relationship/activity fields. There are also a number of fields that you see recurring for every relationship or activity. These are the generic data. These fields exist at a higher level, the parent relationship, and are shown in the daughter relationship. For example, the fields First name and Last name. You will see these fields in every person type. These fields exist at a higher level and are inherited to contacts or employees. The same applies to the Number field within an activity.
​

Now let's see what this means in practice.
​

To set the right permissions, you first need a role. Follow the steps below to create the role:
​

Type of rights
​

Basically, you can set the following permissions. This can be done either at the entity itself or at the field level. Click on the entity name to see the fields.
​

By clicking on a bullet you adjust the entitlement.
​

Furthermore, permissions are divided into a number of different components.
​

Relationship: This is the highest level. When you grant or take away rights at this level, this will be visible in the subsidiary entities linked to it. In the everything section, fields such as IBAN or relationship number are available. At organisation level, fields such as VAT or Chamber of Commerce number can be accessed. At person level, the first/surname or date of birth.
​

Relationship type: One level down, you find the generic data for all relationship types, organisation or person. Think fields like mailing opt-out or former.
​

Organisation types: Below that, you will find the specific data for each relationship type. These are the fields you have added on the map of a relationship type. The commercial relationship types contain some fields that are generic for all commercial relationship types, such as customer and prospect.
​

Person types: The above also applies to the person types. Here, too, we know the common commercial relationship group. We also have the contact group , which contains the generic fields that are available for both a contact and an employee. For example, function or e-mail address.
​

Activities: The everything section contains all generic activity fields, such as subject or number. You will also find all fields per activity type here.
​

Own entities: Here you will find all proprietary entities you have created in Tribe.
​

Pick lists: Here are all the drop-down lists in Tribe.
​

Templates: Here are all the templates in Tribe.
​

Configuration: This group contains the right to widgets and views. If a user has this right, it is possible for him to create widgets and views for the organisation, without administrator rights.
​

General: This group only contains the right to export. If this right is taken away, it will be implemented on all entities in this role.
​

Other: This group contains some entities that are commonly used and do not fall directly into any of the previously mentioned groups.
​

A user can be in multiple roles, the rights within those stack up. If one role has a right on and the other role does not, the role with the right on 'wins'. Each individual employee can see which rights have been set for him based on all roles linked to him.
​

Follow the steps below to view the rights per employee:
​