๐กHow to Use the Hierarchy in Zenput
| The Hierarchy in Zenput is the central place to manage your company's organizational structure โ including teams, users, and locations. It impacts everything from how tasks are assigned to how reports are generated, so keeping it organized is key. The configuration of your company's organization is critical to who and what is getting done in Zenput. With Hierarchy, you will have the ability to manage all this at a glance, saving you valuable time and resources. |
๐ Navigate this article:ย |
What Is the Hierarchy?
The Hierarchy helps you:
- View and manage teams, users, and locations
- Control who sees what
- Assign tasks accurately
- Ensure clean and relevant reporting
- Easily share forms to a specific subset of people
- Create a foundation for setting up alerts
Example Hierarchy Structure:
โถ
France VP
โถ
Paris Region
โถ
Eiffel District
โถ
๐
Store 1351
45 Avenue des Champs-รlysรฉes, 75008 Paris
โถ
๐
Store 1352
128 Rue de Rivoli, 75001 Paris
Your teams are organized in levels, with each level containing the teams below it. For example:
VP Team โ Regional Team โ District Team โ Locations
In the example above, team "France VP" is at the top. Inside it, you'll find team "Paris Region", and within that region is team "Eiffel District". The district team includes the district manager plus individual store managers. Finally, each location (Store 1351 and Store 1352) has its own location owner.
When teams are structured this way, upper levels automatically include everyone below them. The VP sees everything, regions see their districts and locations, and districts see their stores. Forms and notifications flow correctly throughout your organization.
Start at the bottom and work your way up. First, create your locations and assign location owners. Then create district teams and add those locations. Next, build regional teams that contain your districts. Finally, create your VP or enterprise-level team that encompasses all regions and executive staff.
Navigating the Hierarchy
When you open the Hierarchy tab, you'll see your teams organized in expandable sections. Here's what you need to know:
๐ Search
Using the search tool on the Zenput Hierarchy page is a quick way to locate where users and locations are located within their respective teams.
๐ฅ Teams
Teams are denoted by the name of the team in a white bar. Clicking on the arrow next to the team name will expand the view and allow you to see the users that are part of this team, as well as the other teams or locations that roll up into this team. You can continue to use the arrow for any and all subteams and view their information as well.
๐ค Users
Users will be displayed under the teams or locations they are a part of. You can view the user's name, role, and permission. Clicking on the three dots next to the user's name will take you to the user page where you can make changes to edit a user's information.
๐ Locations
Locations will be displayed under the appropriate teams the location reports to. You are able to view which users are part of that location by clicking on the arrow to the left of the location name. Clicking on the three dots to the right of the location will take you to the location's information page where you can edit the location's information.
Creating & Managing Teams
How to Create a Team
|
|
|
|
|
|
|
|
|
|
|
|
|
The end result is a complete hierarchy with nesting teams.
ย
How to Edit a Team
Please note: There are several things you should be aware of when editing teams. Tasks, projects, and follow-up task/alerts can be set up by team. Adding or removing users from teams can affect those actions too.
For example: If you remove the Area Manager from the team 'Area 1234', and alerts are sent to the role 'Area Manager', no one will then receive the alerts set to go to the Area Manager for Area 1234.
|
|
|
|
|
How to Delete a Team
|
|
|
Managing Users
Users appear under their assigned team or location. You'll be able to see their name, role, and permissions.
How to Create a User
This is also where you can invite new users.
|
|
|
|
|
|
|
|
|
|
|
How to Edit or Delete a User
|
|
|
|
|
|
|
Managing Locations
How to Add Locations
|
|
|
|
|
How to Edit or Delete Locations
|
|
|
|
|
Important Notes & Best Practices
Critical Hierarchy Rules:
- Users can see/complete work on the team as well as any team below them in the hierarchy, to which they are assigned.
- It's best practice that users and locations are only on one team at a time - in the event a user or location is placed on multiple teams, it might result in errors when work is assigned.
- Only one user with a specific role can be on each team. For example, one team cannot have two 'District Managers' (an exception here is in case you assign each of the district managers to their respective locations).
- All users must be assigned to a team to receive tasks.
Important: Any hierarchy changes will affect project/task assignments within 48 hours for Daily projects and on the next occurrence for other recurring instances such as weekly and monthly tasks.
Impact on Alerts: Tasks, projects, and follow-up task/alerts can be set up by team. Adding or removing users from teams can affect those actions. For example, if you remove an Area Manager from a team and alerts are sent to that role, no one will receive the alerts for that team until a new Area Manager is assigned.
Comments
0 comments
Please sign in to leave a comment.