Sensitive follow-ups
Leave documentation or a workplace concern needs a sentence on the file that is not a Slack DM.
HR-only notes
Private context that does not leak to the team view.
People ops sometimes needs a note that is not for the manager and not for the employee. Staffquorum keeps that space on the file — behind a role.
Why it matters
A conversation about an accommodation, a counseling note, or “call before you email this person” should not appear next to a timesheet. Managers get the work they need. They do not get the private file.
HR-only notes attach to the employee record and are visible to operator roles you grant. They are not in the manager queue, not in the employee profile they see, and not in a birthday digest. Opening or editing a note is an audit event, the same way opening a sensitive document is.
Join the waitlistEmployee file
HR onlyNote on Priya Shah
Prefers email before phone for leave follow-ups. Intermittent leave documentation is on the file — do not discuss in the manager queue.
Visible to operators. Hidden from Maya Chen (manager) and from Priya’s own view. Last opened by Elena Brooks · today 8:41 AM.
On the record
What you get in Staffquorum.
- Notes scoped to people-ops roles, not the manager default.
- Invisible to the employee’s own view.
- Stored on the record so they survive a ticket-system wipe.
- Audit events when a note is opened or changed.
- No mixing with public manager tools or help articles.
How it runs
A week in this workflow.
01
Write on the file
An operator adds a note with enough context for the next person who covers the desk.
02
Keep the audience small
Manager and employee views never include the note. Granting extra access is explicit.
03
Leave a trail
If someone opens it, the product can show who and when. That is how you answer a later question.
Who uses it
Built for the jobs you already have.
Coverage between operators
When a second people-ops person steps in, the note is there. The manager still sees only their queue.
Related
These workflows share the same record.
People directory
One employee record. Searchable. Owned.
Name, job, site, manager, documents, and status sit on a single file. The directory is how you find someone — not a Friday export from payroll.
Roles and access
Who can open a file is a product decision.
Operators, managers, and employees do not share a login. Sensitive fields sit behind roles you can explain to counsel — and to the person whose file it is.
Documents
Files on the record, not in a drive named HR_SHARE.
Offer letters, handbooks, I-9 packets, and signed acknowledgements attach to the employee. Access follows the same roles as the rest of the product.
Manager tools
Approvals, coverage, and birthday emails that stay private.
Managers get the queue they already run: time exceptions, leave requests, and who is out. Birthday dates stay on the file — not a company-wide calendar.
Want this workflow on your roster?
Tell us your headcount and what you run today. We will write back from hello@staffquorum.com when we can show you the product.