This introduction article will help users set up Acct/Dept parent-child relationships.
Overview
When defining accounts and departments, you can set a parent relationship between two accounts, which creates a hierarchy.
Where to Find This
Navigate to parent-child relationships following this path:
- TDAdmin > Organization Settings > Acct/Dept
- TDNext > People > Accounts
Defining an Account/Department Relationship
Users must have the Modify Account/Department Hierarchy global permission to modify the Parent field in TDNext.
Users can define an Account/Department hierarchy by setting a parent relationship on each account when editing or creating the accounts.
Creating a New Account/Department
TDAdmin
- Navigate to Organization Settings > Accounts/Departments.
- Click the +New button in the Accounts/Departments Display window.
- In the New Account/Department popup window, set the Parent field to any existing account.
- Fill in the required and optional fields as desired.
- Click the Save button.
TDNext
- Navigate to the People Application > Accounts.
- Click the +New Account button in the Accounts Display window.
- In the New Account/Department popup window, set the Parent field to any existing account.
- Fill in the required and optional fields as desired.
- Click the Save button.
Updating an Existing Account/Department
TDAdmin
- Navigate to Organization Settings > Accounts/Departments.
- Click the Name link of the account that you’d like to edit.
- In the Edit Account/Department popup window, set the Parent field to any existing account.
- Click the Save button.
TDNext
- Navigate to the People Application > Accounts.
- Click the Name link of the account that you’d like to edit.
- In the Account Display popup window, click the Edit Account button.
- Set the Parent field to any existing account, then click the Save button.
Using Account/Department Relationships
Account/Department Hierarchies can be used for reporting, as well as restricting user visibility.
Reporting Based on Account/Department Hierarchies
Report sources which include account or department information support reporting on the Account/Department hierarchy.
The following report sources support reporting on the parent account of the selected account and support filtering on the Account/Department hierarchy of the selected account:
- Actual Hours
- Assets
- Configuration Items
- Contracts
- Expenses
- Issues
- People
- Plans
- Projects
- Project Requests
- Projects and Requests
- Risks
- Scheduled vs Actual Hours by Project
- Survey Response
- Task
- Ticket
- Ticket Task
The Account report source also supports reporting on the full Account/Department path (i.e., all parent accounts, up to the root account) and listing an account's children accounts.
Visibility Based on Account/Department Hierarchies
The View People from All Accounts/Departments permission is automatically assigned to everyone. Users without this permission have limited visibility to other users in the system, based on their assigned accounts. These users will only be able to see a person record if that person record has an account that matches the user's accounts or is a child or descendant of one of their accounts. By removing this permission from users, you can restrict their visibility of the People database to the records that are more closely related to their role.
These visibility restrictions apply in the following places:
- Typeahead fields and lookup pages that include Customer records in TDNext and TDClient.
- For example, this includes the Requestor field, but does not include the lookups for project members.
- Search results in the People application .
- People report source.
This visibility restriction does not apply to Person Detail pages.