Skip to main content
All CollectionsWhat's new?
Directory: Qulture.Rocks Organogram Tool
Directory: Qulture.Rocks Organogram Tool

Check out how the organogram function works in Qulture.Rocks and the information that the Directory provides. 😎🎁

Updated over a week ago

1. What is the Directory?

πŸ‘‰ The Directory is the version of the company's organogram in the platform. Through it, employees can access the profile of all their colleagues, enabling greater interaction among each individual in the organization, as it is available for any type of relationship in the system.

The structure follows the visualization of a hierarchical tree of leadership, as shown in the image below:

πŸ‘‰ To access it, simply click on the Directory icon in the sidebar that contains the platform modules.

🟣 Note: users with the role of General Admin or Company Admin can also view it through the path: Organization Profile > Directory.

2. Who has access to this functionality?

Currently, the functionality is available to all employees within the organization, each with their level of viewing permissions.

Features

3.1 Card Summary

Each selected employee card contains key profile information, as shown in the example below:

🟣 Photo

🟣 Current position

🟣 Position criticality (visible only to direct and indirect leaders and admins)

🟣 Tags (according to admin permissions)

🟣 Hierarchy: who is the leader and the number of subordinates

3.2 Basic Profile of the collaborator

When clicking on a collaborator's card, it is possible to view the fields according to the permissions assigned by the admin in Organization > Fields and collaborator profile > Collaborator fields.

The basic information visible to all relationships includes:

🟣 Manager position, managed position

🟣 Job title

🟣 Position ID

🟣 Photo, name, email

Also, please note that the sections and fields will appear based on the configurations set in the Basic Profile and the permissions assigned to each field during its creation/editing.

4. Important settings for admins

4.1 Relationship Manager > Direct Report

In order for the Directory to include all hierarchical levels within the company, it is necessary to establish the Manager > Direct Report relationship within the configuration of the employee table.

🟣 If you are unsure how to include the leader of the employees, you can access this article for more information.


4.2 Collaborator Field Permissioning

The visibility of Collaborator Fields' content will follow the permissioning rules established by the admin during its creation or editing. Therefore, it is important to select which type of relationship can view each field to avoid issues with confidential information.

πŸ‘‰ To configure, simply follow the path: Organization Profile > Collaborator Fields and Profile > Collaborator Fields > Click on 'New Collaborator Field' or edit an existing field using the pencil icon > Relationship Permissions.

5. Search Field

In the Directory search field, you can only identify collaborators by their name and search one at a time.

6. Important Alignments

🟣 With the activation of the Directory, the old organizational chart is no longer available, and access is exclusively through the new icon in the platform's side menu.

🟣 It is not possible to select whether a collaborator's profile will be available or not, as all profiles are visible in the Directory (including the Qulture Admin's).

🟣 Organizations that have chosen not to allow visibility of the organizational chart will not have access to the Directory immediately after its launch. If interested, you can inform your Customer Success Manager (CSM) to enable it.

🟣 If you wish to change the name of the Directory in the platform, you can contact the #ChamanoChat team to make the change.

🟣 The visibility of the content in the collaborator's fields will follow the permission rules set by the admin.


After reading this, do you still have any questions? #CallUsOnChat! We are here to assist you throughout your journey with Qulture.Rocks πŸ˜‰

Did this article help you find what you needed? Please leave your feedback below so that our team can continue to improve πŸš€βœ¨

Did this answer your question?