Within a CRM system, you share relationship data and related activities with your colleagues. This way, everyone is aware of what is going on with your relations and you can forward activities to each other. However, there are reasons why it is desirable not to share certain data with each other. If this is the case for you, perhaps using teams is the solution.
​

Very simply put, a team is a group of employees. For example, team sales or team support where the right people are assigned to the right team. Defining a team and its employees has a lot of added value when you don't want to share certain data from the CRM with the entire organisation, but only with members of your team.
​

Teams vs roles & rights
​

When it comes to shielding data, you might quickly think of roles & rights. What is the difference between teams and roles & rights?
​

In a role, you define the different rights of an employee in that role. For example, the right to create or modify customers, or the right to see and edit a sales opportunity. When I don't have the right to see sales opportunities, I also don't see the sales opportunity under the plus button or in a relation's timeline. This activity does not exist for the user in this role, so to speak.
​

But what if I too should be able to use the sales opportunity activity, but I am only allowed to see sales opportunities from team Netherlands and not sales opportunities from team Europe and vice versa? Then using only roles no longer suffices and you also use teams.
​

Within the teams, we distinguish between masking off all data per team, i.e. masking off both relations and activities, or masking off only activities per team and still sharing the relations with the rest of the organisation. When creating data, a team is automatically linked in the background, making this data visible or invisible to other users of the CRM.
​

You can read how this works in the following chapters.
​

Building on the previous example. My organisation consists of a team Netherlands and a team Europe. Within the CRM, we share all relationships with each other, so everyone has access to all customer and contact data. The exception is activities. Team Netherlands is only allowed to see its own sales opportunities, tasks, appointments, etc. The same applies to team Europe.
​

Follow the steps below for the correct setup for this example:
​

Members of this team now see all relations within Tribe CRM. This setting also ensures that, no matter whether team Netherlands or team Europe creates the relationship, it will not be linked to a team. When creating an activity, the team of the current employee is linked, which protects it from members outside this team.
​

The team field is not visible by default in the details of a relation or activity. It is filled in the background. An employee therefore does not have to choose between the different teams.

A second example. My organisation again consists of team Netherlands and team Europe. Within the CRM, we do not share anything with each other, so neither relationships nor activities are protected. Each team creates its own data and only shares it among themselves within the team.
​

Follow the steps below for the correct set-up for this example:
​

Members of this team now only see their own relations and activities. This setting also ensures that, when creating the relation, the employee's current team is linked immediately. This protects it from members outside this team. All activities created under this relation are linked to the same team as the relation. Again, the team field is not visible by default in the details for a relation or activity. It is filled in the background. So an employee does not have to choose between the different teams himself.
​

Note: If you use this setting, there is a possibility that relationships are created several times by different teams because this relationship is not visible to everyone.
​

The above settings apply to users, but what about a manager? In the above situations, for example, the person ultimately responsible for sales. My manager wants to see the relationships and activities of team Netherlands as well as team Europe.
​

In this case, you can go three ways.
​

Situation 1
​

In this situation, the manager will have to switch between both teams to look up and create data. This means that when creating new data, the team field is automatically populated with the selected team in the background.
​

When creating reports, the manager must bear in mind that he has to create two separate reports, because in this situation no overarching insight into the data is available. The data is only available per team.
​

Situation 2
​

In this situation, the manager does not have to switch between teams because he has access to the data of both teams. It is therefore possible to create one report with data from both teams.
​

However, when creating data, he has to select the right team himself in the dialogue. If the team is not linked, the record is not visible to members from both teams.
​

Situation 3
​

In this situation, the manager can step in and out of a team because he also has administrator rights. If no team is selected, all records are visible. It is then possible to create a report with data from both teams. It is also possible to view data per team.
​

Two methods can be used to create data.
​

Note: The team settings are saved in the user's browser cache. After changing team settings, it is necessary for the user to refresh the cache.