Sample data · this company and its people are invented.
Company import
Key shown once — copy it now
Each person’s consent
Each consent control below represents that person’s own personal-key sign-in. The source administrator cannot choose consent for someone else. Named-data consent starts off.
Consent is only as strong as claim-code custody: root or a managing node that obtains and redeems the person's onboarding claim code can hold that personal key and consent with it. Each consent change writes a subject notice as well as an audit row. Withdrawal affects future snapshots; it cannot recall an earlier snapshot.
Source administrator · issue an export key
The source administrator issues a one-time export key after each person has made their choice. The key is consumed by the company’s preview pull.
1. Choose where the imported team lands
2. Preview and resolve clashes
Non-consenting people do not become named People rows. Matching text IDs never merge automatically. Map explicitly or create a new identity.
| Incoming person | Existing person | Resolve clash |
|---|
3. Import checks and handoff
- Event keys and content fingerprints prevent duplicate events. Unresolved duplicates are flagged.
- Original list-price costs and pricing versions stay attached. History is never silently repriced.
- Closed monthly figures stay frozen.
- Access follows holder keys and the dated organization branch. Source keys do not move.
- Import and every explicit ID mapping are audited on both servers.
Pull the preview and resolve every clash before importing.
Imported. Open People to see imported people.
imported, not counted until they sign in here
They must also upload with their own credential here during the report window.