Setting up organigram for authorization
The organigram determines what users see in the dashboards. This article describes how to set up the organigram and how to link users to it.
Loading source systems
In most organizations, multiple software systems are used for different purposes. Often these systems have their own organigram and their own permission structures. In dashboards where multiple source systems converge, this creates problems. For this reason, SalureConnect offers the possibility to link all organigrams from underlying systems into 1 overarching organigram.
The first step that must be taken to do this is to set up the source systems. This is a simple job that can be done by the application administrator, or someone else with the appropriate rights:
- Navigate to Settings > Authorization > Source systems;
- Add a new source system and give it a recognizable description;
- Open the source system just created and navigate to the Entities tab;
- In this tab, now add all entities with their code and description as they are stored in the source system.
Setting up organigram
The organigram in SalureConnect is set up in three steps.
- Create layers - Determine how many layers the organigram consists of and what they are called;
- Add Entities - Set up the actual organigram;
- Link source systems - Link the organizational units from all source systems to the organigram in SalureConnect.
1. Creating layers
- Navigate to Settings > Authorization > Organigram layers;
- Now add as many layers as needed and give each layer a recognizable description. Always start with the top layer. The numbers of the layers are added automatically and have no function except recognizing the layer.
An example of an organization with 3 layers could be: Organization, Region, Location.
2. Add Entities
- Navigate to Settings > Authorization > Organigram;
- The page that now appears is empty. Click on the blue plus sign to add the first entity. For example, if the first layer is called "Organization," add the organization name here;
- Now fill all the underlying layers and create all the entities needed. The organigram does not have to match the organigram from a source system. It is best when the organigram in SalureConnect is the same as the actual organigram.
3. Linking source systems
Once the organigram is actually set up, it is time to link the source systems to the organigram:
- Click an entity in the organigram. An information block appears on the right with three tabs: "Linked," "Not Linked," and "Linked Elsewhere." Open the "Not Linked" tab;
- Find the source system entities belonging to the selected entity and tick them. Note that the selected source system entities then move directly to the "Linked" tab;
- Now click the next entity in the organigram. Note that the "Elsewhere Linked" tab is now populated. When the user opens this tab, the source entities that have just been linked are visible;
- Again, open the "Not linked" tab and link all source system entities;
- Do this for the entire organigram until the "Not linked" tab is completely empty.
It might be wise to create 1 entity in the organigram called "Archive", or something similar. To this entity all source system entities can be linked that are no longer in use but have not been deleted from the source system.
Linking Users
A detailed description of creating and managing users can be found on the page on this topic. For now, just a description of linking users to the organigram you just set up:
- Navigate to Settings > Authorization > Users and open a user;
- Click on the "Organigram" field and the organigram will open. Here tick the appropriate place the user belongs to;
- It is possible to deviate from the default place in the organigram at the dashboard level. For example, an HRM advisor may be in the HRM department in the organigram, but still have all rights in the HRM dashboard. For a financial dashboard, on the other hand, this person would then be able to see only their own department.
Authorizing dashboards
The operation of dashboard authorization is detailed in the article "Activating authorization on data".
When users are linked to the organigram, this organigram can also be linked to dashboards. In this way, users only get to see the information to which they are entitled according to the organigram in SalureConnect.
Example: user Taylor has access to the Sales department in the SalureConnect organigram. Cost center 100 and 200 from Profit are linked to the Sales department. When Taylor gains access to the "Sales figures" dashboard in which Cost centers 100 and 200 are also included in the data, she gains access to the data linked to these cost centers and not the other data.
The application administrator can link the organigram and permissions to dashboards by including a Section Access component. The Section Access code looks like the following and should be added in the dashboard:
Code Section Access
Related Articles
Setup Organigram
The organizational chart determines what users see in the dashboards. This article describes how to set up the organizational chart and how to link users to it. Loading source systems In most organizations, multiple software systems are used for ...Users
This article describes how to add users and how to assign them appropriate permissions. Add user Navigate to Settings > Authorization > Users; Click on "Add User" in the upper right corner of the table; In the screen that follows, enter a name and ...User management
This article describes how to add users and how to assign them appropriate permissions. Add a user Navigate to Settings > Authorization > Users; Click on "Create" at the top right of the table; In the screen that follows, enter a name and email ...Roles
Authorization can be set up per user, but it is better to do it through roles as much as possible. A role can be associated with multiple users. This makes it possible to easily modify the rights of groups of users in one place. Creating a role ...Creating an API token
For the most part, the data stored in SalureConnect can also be retrieved via REST APIs. Of course, authorization also applies here. This article describes how to create an API token. The article "REST API" describes how the REST API can actually be ...