Overview
The Company Hierarchy feature allows Tenant Admins to easily manage organizational reporting structures within Bigtincan Meetings. This feature supports importing your company's organizational chart through a universally supported CSV file format, provided by most HR systems (ADP, Workday, Salesforce, etc.).
Applying the company hierarchy affects meeting visibility, enabling managers and admins to view meetings of employees who report directly or indirectly to them.
Accessing Company Hierarchy
- Log into your Bigtincan tenant account as a Tenant Admin.
- Click your Account Dropdown in the upper-right corner.
- Select the option "Company Hierarchy".
Uploading Company Hierarchy CSV
On the Company Hierarchy page, you can upload a CSV file that defines your organization's reporting structure.
CSV Requirements
Your CSV must include the following columns:
Column | Description | Example |
user_id (required) | Unique identifier for each user | 123456 |
manager_id (required) | Unique identifier for each user's direct manager | 654321 |
email (required) | User’s email address (used for matching existing Bigtincan accounts) | user@example.com |
Note:
- The CSV file must include headers exactly as listed above (user_id, manager_id, email, name).
- Only users with active licenses in Bigtincan will be matched and integrated.
CSV Upload Process
- On the Company Hierarchy page, click the "Manage hierarchy" button.
- Browse or drag your CSV file to upload.
CSV Validation and Error Handling
After uploading, Bigtincan will validate your file and check for possible issues.
Types of Issues Detected:
Critical errors (Hierarchy can still be applied):
# |
Error Type |
Description |
Result |
1 |
user_id is missing |
User record does not include a user_id. |
User not processed |
2 |
Missing email |
User record does not include an email. |
User not processed |
3 |
Duplicate user_id |
User_id appears more than once in the CSV. |
User not processed |
4 |
Duplicate email |
Email appears more than once in the CSV. |
User not processed |
5 |
Email not found in BTC Service |
Provided email doesn't match any existing licensed Bigtincan user. |
User not processed |
6 |
User cannot be their own manager |
User's manager_id matches their own user_id. |
User not processed |
7 |
Manager not found |
Provided manager_id does not match any user_id in the CSV. |
User processed (User is included without a manager, sees only their own meetings.) |
8 |
Cannot establish relationship, manager is missing |
No manager_id is provided for a user. |
User processed (User is included without a manager, sees only their own meetings.) |
9 |
Circular manager relationship detected |
Two or more users are subordinate to each other. |
All affected users have not been processed |
Non-critical Warnings (Hierarchy can still be applied):
- Missing Manager: The specified manager_id does not match any existing user.
- Manager Not Specified: User has no manager (manager_id left blank).
How Users with Errors are Processed
- Not Processed:
Users with critical errors (1-6, 9) are excluded entirely from the hierarchy. They continue to have standard access but are not part of the structured hierarchy, and they only see their own meetings. - Processed without a manager:
Users with non-critical errors (7-8) are included in the hierarchy without any manager assigned. They will not have any subordinates and will see only their own meetings.
Please Note: When no users in the CSV match existing users in Bigtincan, then the CSV is not going to be applied.
Handling Errors
- The system lists detected errors and warnings with detailed explanations.
- Critical Errors and Non-critical warnings can be accepted, but we recommend correcting them for the clearest organizational view. Correct errors in your CSV file, then re-upload for accurate hierarchy representation.
Visualizing Company Hierarchy
After successful validation:
- Click the "Generate Visualization" button to display your organizational hierarchy visually. Generating Visualization will then show you the different branches of the company hierarchy in a diagram, like seen below.
- The interactive visualization provides:
- Expandable branches showing dependent employees reporting directly or indirectly.
- Easy search and navigation through the hierarchy.
- A scrollable view to manage extensive org structures.
How the Company Hierarchy Affects Meeting Permissions
Once the Company Hierarchy is applied:
- Tenant Admins and Managers see:
- Their own meetings.
- Meetings of employees who directly report to them.
- Meetings of employees further down the reporting chain (multiple hierarchy levels).
- Without applying the hierarchy, users can only see their meetings.
Note:
Only Tenant Admins can manage and upload the Company Hierarchy. Regular users do not have access to this functionality.
CSV Upload History
The platform saves the history of your last five successfully applied CSV uploads.
- History Includes:
- Date and time of upload.
- The user who uploaded and applied the file.
- Ability to download previously applied CSV files.
- Option to reapply a previously uploaded CSV file.
- Amount of users being processed
- The number of errors appeared
- Important:
CSV files uploaded but never applied (e.g., visualization not generated, modal closed) are not saved in history.
Viewing and Restoring History
- Navigate to the Company Hierarchy section from your account dropdown.
- Click “Manage hierarchy”
- In the lower section, view the "History" list:
- Date and Time of upload.
- Uploaded by (user’s email).
- Button to download previously applied CSV.
- Button to replace the currently applied CSV with the selected document from the history list.
- Button to delete the selected CSV.
- NOTE: if an applied file is deleted then no company structure will be applied to the team meaning the users will only see their own meetings.
Current Limitations
Currently, CSV uploads and updates are manual. Automated daily uploads (via SFTP or API) are being considered for future releases.
Best Practices
- Regularly export and upload updated CSVs to accurately represent your company's reporting structure.
- Immediately correct critical errors to ensure a successful and accurate application.
- Regularly review the upload history to maintain transparency across admin teams.
Comments
0 comments