Customers and identity
The Systems that let customers in and keep their consent and privacy requests.
The Systems in this group let each Customer sign in to their own Tenant, and keep their consent and privacy requests. A Customer that is a company gets teams, single sign-on and directory sync from the first deal.
The Systems
| System | What it does | Say |
|---|---|---|
| Customer access | Members, invitations, Permissions, single sign-on and directory sync per Tenant | "Let a customer invite their team" |
| Privacy | Each Purpose for personal data, recorded Consent, and access and deletion requests | "Delete everything held about this person" |
Selling to a business
A business Customer gets one Tenant. Their admin invites the team, and an IT admin connects SAML or OIDC through a setup link, with no call to you. Their own directory adds and removes people as it changes, and every change lands in the audit log.
Privacy requests
A deletion or access request is answered across every System inside its legal deadline. Data is masked in place, so Ledger totals and tax records stay whole. Privacy wakes when the Startup records its first known person.
Who runs it
The Security Engineer owns Customer access and the Privacy Officer owns Privacy. Let customers sign in is the guide for a new App.