Within this article
- New role at the entity level: Entity Administrator
- Evolutions to the Country master filter in Data Stories
.
New role at the entity level: Entity Administrator
.
Presentation of the Entity Administrator role
At the moment, only the Company Administrator can create, configure and modify entities which can represent an important workload and a dependency from the entities towards the parent entity. To alleviate this situation and give more independence to entities, we have created a new role at the entity level: Entity Administrator.
The Entity Administrators will be able to edit the existing entities (including their sub-entities) to which they are assigned.
In terms of rights on the platform, this role becomes the first level role at the entity level, with more rights than the Entity lead. It means that the Entity Administrator can carry out the sames actions, and more, than the Entity Lead.
|
Also, as company role and entity role are cumulative, if the Entity Administrator has a role at the Company level with more rights, like a Company Administrator role, then they will benefit from these larger rights. To know more about collaborator roles, please read the dedicated article. |
.
Creating an entity and assigning an Entity Administrator to it
Company Administrator users are the only ones who can create a new entity (as currently the case) and assign an Entity Administrator to an entity (from the Entity employees tab of the entity form).
|
Assigning an Entity Administrator to an entity isn't mandatory. If you don't need to add this level of entity management, you can leave the field empty. On the other hand, if needed, a user can be assigned as an Entity Administrator to several entities and can cumulate other roles. |
|
As a reminder: A collaborator with the Operational role on at least one entity will not appear in the selection of the other roles, and vice versa. |
.
The view of an Entity Administrator
As previously mentioned, Entity Administrators can manage and modify their assigned entities, including their sub-entities. To do so, they can click on the Entities menu in order to access the list of entities.
Then, on the entity tree structure page, they will see an information message at the top, listing the entities they are assigned to. They will see them as active, but the others entities (to which they are not assigned to) will be grayed out, non-editable, and employee names will be hidden from the entity card for confidentiality purposes.
By clicking on an entity name in the information message, they will be redirected to the entity and its sub-entities in the tree structure.
On the entities they are assigned to, Entity Administrators will be able to open the action menu in the top right corner of the entity card to open the page to edit the information. However, other actions like adding a sub-entity, duplicating, or deactivating the entity are exclusive to Company Administrators.
When editing an entity, the Entity Administrators will be able to modify the information present in each tab of the form:
- General information
- Billing contact information (for legal entities only)
- Entity employees
- Spending lines and workflows
- RFPs settings
| There is only the Entity Administrator field that can't be modified by the Entity Administrator themselves, but only by the Company Administrator). |
Evolutions to the Country master filter in Data Stories
Until now, when you were using the Country master filter on your data in the Data Stories module, it was the country set on the entity issuing the RFP. As from this release, the country used to filter the data will be the one filled on the RFP form by the Operational manager.
It means that, in case multiple countries are used on a same entity, the activity can now be filtered by the countries where the project is actually taking place.