The job of this console
Find the person, store or retrieve a permitted file, and keep sensitive scans off tickets and graph snippets.
People · Records
Documents
Employee document vault — contracts, IDs, and files on the person — with masking and retention, not a public drive.
Scroll to Flowcharts. Scenario: Upload an employee document.
People vault
Files that belong to the employee record
Documents is the vault on Employee. Categories, retention, and persona masking apply. It is not Drive-for-everything.
People → Documents
Route
/people/documents
Org flag documentsEnabled
HR Admin · Manager (scoped)
Seat at the table
HR and scoped managers. Employees may self-serve some categories during onboarding. Executives do not browse everyone’s IDs.
The working rhythm
Search employee, open vault, upload or download, close. Confirm retention on sensitive types.
Moments that bring you here
Contract renewal. ID expiry. Onboarding upload. A subject-access request.
ⓘ
Sensitive attachments
Do not persist raw bank, tax, or medical content in AI audit logs or Work Graph metadata.
Flowcharts
1 — File a people document
Find the employee, upload into the vault category.
flowchart TD
A[Open Documents] --> B[Find Employee]
B --> C[Choose category]
C --> D[Upload / open]
D --> E[Retention + masking]
E --> F[Source remains Employee vault]
- 1OpenPeople → Documents.
- 2Find personEmployee source.
- 3UploadCategory and policy.
- 4ProtectNo raw copies in AI or graph snippets.
Overview
People documents are the employee vault. Project files stay on project file manager. Leave medical evidence has leave document rules.
How to use
1. Right vault
Project SOWs are not people documents.
2. Masking
Bank and medical stay restricted.
3. Retention
Honor holds; do not email a personal archive.