What a user can see and do can be influenced by their Memberships within larger entities. You can add a user to a number of other entities, including:
|Organization||Primary organizational unit (companies, subsidiaries, etc.)|
|Department||Functional unit (accounting, administration, marketing, IT, etc.)|
|Location||Physical/geographic unit (cities, sites, buildings, offices, rooms, etc.)|
|Group(s)||Role-based unit (end users, managers, technicians, etc.)|
These entities structure the user base to provide the overall framework for capturing and reporting information related to users and issues within your system.
Using entities to influence a user’s experience is also optional. For example, users that belong to a certain organization may see a different Site Title and Site Colors. Users that belong to a certain department may see only issues submitted by or assigned to other members of their department. Users that belong to a certain group may see additional Quick Picks, Issue Types, and Tasks that cannot be seen by other users.
The table below shows the field and object filters that can be controlled at the entity level.
|You can define user access to specific...||Based on Organization||Based on Department||Based on Location||Based on Group|
|Issue Types & Subtypes||✔||✖||✖||✔|
|Knowledge Base Articles||✔||✖||✖||✔|
|Site Title and Logos||✔||✖||✖||✖|