View-Only Headcount Permissions
Last updated: May 5, 2026
View-only permissions let you give users visibility into headcount without allowing edits.
Use this feature to safely share hiring plans, approvals, and headcount data with stakeholders who should not modify records.
Why this matters
Before this feature, anyone who could view headcount could also edit it.
Now you can:
Prevent accidental edits
Limit access to sensitive information (like comments)
Give broader visibility without losing control
How it works
TeamOhana separates visibility from edit access.
You define access using:
Scope – What headcount a user can see
Access level – What details they can see
Headcount visibility scopes
Scope | What users can see |
All headcount | All headcount within their access (ABAC) |
Reporting line | Headcount in their reporting hierarchy |
Assigned | Headcount where they are a recruiter, manager, or collaborator |
Permission types
Each scope includes two permission options:
View with comments
Users can:
View full headcount details
Open the headcount details drawer
See comments and audit history
Users cannot:
Edit any fields
Assign recruiters
Update job descriptions
Perform inline edits in Hiring Plans, Requests, or Approvals
Take bulk actions (e.g., bulk approve, bulk update)
View without comments
Users can:
View basic details in table view
Users cannot:
Open the headcount details drawer
See comments or audit history
Edit any fields
Perform inline edits
Take bulk actions (e.g., bulk approve, bulk update)
Important rules
You can enable only one permission per scope (with or without comments)
Manage permissions include view access automatically
View-only users can never edit headcount or take bulk actions
How view-only permissions affect the UI
TeamOhana enforces read-only behavior across the product.
Headcount details
Hides the Edit icon
Disables editable fields (including hiring details)
Prevents opening the drawer (for “without comments” users)
Hiring Plans, Requests, and Approvals
Disables all inline edits
Disables bulk actions
Hides audit history if comments access is restricted
Scenarios
Disables editing
Hides comments when not permitted
Inbox
If a user does not have comment access, they see:
“You do not have permission to view comments. Please contact your administrator for access.”
Interaction with manage permissions
Manage permissions always take priority.
Users with Manage All / Reporting Line / Assigned:
Can view and edit headcount
Can perform bulk actions
Automatically get view with comments access
Users without manage permissions:
Cannot edit anything
Cannot take bulk actions
Cannot request new headcount
If a user does not have manage access, TeamOhana disables the Request new headcount option to prevent incomplete workflows.