Employees
Their daily workspace and permitted employee-facing information.
A shared operating system needs clear limits. Personal, corporate and sensitive information have different audiences and different purposes.
Permissions should reflect the role and the information needed for its work.
HR, security and psychological context require controlled handling and interpretation.
People retain responsibility for how data is accessed, interpreted and used.
The platform overview describes separate visibility rules for sensitive records. These examples explain the internal model.
| Information layer | Permitted audience | Visibility boundaries |
|---|---|---|
| Integrity checks | Security | Managers see status only. Employees do not see the restricted record. |
| Security & OSINT notes | Upward manager chain + Security | Access follows the specified hierarchy. Employees do not see these notes. |
| HR insights & exit interviews | HR | Restricted to HR; neither managers nor employees see the records. |
Their daily workspace and permitted employee-facing information.
Team information, goals, requests and permitted status views. Manager access does not imply access to restricted HR records.
People administration and designated HR records.
Integrity checks and designated security records.
Configured administration permissions. Company Admin, HR Admin, Payroll Admin and other roles can be combined.
The source describes stackable roles, custom access levels and a DNA-view-all permission. Multiple roles may affect a person’s access. This page is a product overview, not a legal privacy notice or certification claim.
DNA helps support people and interpret context. It is never used for promotion or termination decisions. AI-generated interpretation requires human review and is not a medical diagnosis.
Explore the intelligence principles