Accounts records the people and companies your organisation works with, including internal staff, external individuals and company personnel.
The organisation's world is larger than its payroll: the consultant embedded for six months, the visitor on Tuesday, the partner company whose engineers share your sprints. The account layer holds everyone the business recognises — one governed identity record per person or company, related to everything they touch.
What you record
The three sides of the layer
Internal people — your staff, the people on the payroll side. Their account records connect to their employee records and carry their access.
External individuals — visitors, consultants, partners: the outside people with a real relationship to the business. They carry records, relationships, and — where your operation enables it — scoped access to the platform.
Companies and their personnel — the partner companies, clients, suppliers as recognised entities, with their people related to them: the company's relationship to the business and the person's relationship to the company, both held in one structure.
The account record
| Field group | What it holds |
|---|---|
| Identity | The name, the type — which side of the layer this account lives on |
| Classification | The categories your operation defines (partner, consultant, visitor, client...) |
| Connection | The link to the employee record (for internal people) or the company (for external personnel) |
| Access | Where enabled: the account's access, scoped to what the relationship requires |
| Features | The characteristic stack — certifications, clearance levels, affiliations, per your definitions |
| Contact | The addresses, electronic and postal, with a main address |
The scoping is the trust point: the consultant sees the project they consult on; the partner's engineer sees the work they share. Access is configured for the relationship — use an identified account and the configured permissions. Check the available action trail when reviewing participation.
What you can do
- List, search, filter — by type, category, company, status; bulk actions
- Create, update, view — the standard patterns; the validation and permissions configured for the operation
- Manage company personnel — people related to their companies, both governed
- Scope access — where your operation enables external participation, per relationship
- Relate — the wiring below
What it connects to
| Target | Examples |
|---|---|
| Employees | The internal person's record |
| Companies | The external personnel's employer/partner entity |
| Works & projects | The shared work the external participant contributes to |
| Content & media | The documents and files the account owns or is subject of |
| Addresses | The account's contact addresses |
Where it feeds
The 360° layer is the identity floor under everything that touches the outside: attendance of external participants, scoped participation in shared work, attributable actions on shared records. The accounts platform story is the buyer page; this manual is the identity surface.
The pattern note: same four-part structure — record, do, connect, feed. The accounts manual is where the scoping pattern shows: access that follows relationship, with every action attributable to a governed identity.
Implementers scope the external access to your operation's real relationships at adoption — which consultants see which projects; consultants help define the identity types your business recognises.
No record is an island
Every account relates to the person it extends, the company it belongs to, the work it touches. The identity layer is the relationship layer seen from the door — everyone the business recognises, held as one governed, connected world.
Review the record and its context before deciding what to do next.
Employees → · Organization → · All manuals → · The Accounts platform page →
Check your work
Before granting access, identify the person, their company relationship and the work they need to see. Confirm the assigned role and test that access with the relevant account. A relationship record supplies context; it does not by itself grant permission.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.