# Customers and identity

URL: /systems/customers-and-identity · Id: `page:systems/customers-and-identity`

> The Systems that let customers in and keep their consent and privacy requests.

The [Systems](/business/nouns/system) in this group let each [Customer](/business/nouns/customer) sign in to their own [Tenant](/business/nouns/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](/systems/customer-access) | Members, invitations, [Permissions](/business/nouns/permission), single sign-on and directory sync per Tenant | "Let a customer invite their team" |
| [Privacy](/systems/privacy) | Each [Purpose](/business/nouns/purpose) for personal data, recorded [Consent](/business/nouns/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](/systems/ledger) totals and tax records stay whole. Privacy wakes when the [Startup](/business/nouns/startup) records its first known person.

## Who runs it
The [Security Engineer](/agents/engineering/security-engineer) owns Customer access and the [Privacy Officer](/agents/legal/privacy-officer) owns Privacy. [Let customers sign in](/products/app/let-customers-sign-in) is the guide for a new [App](/business/nouns/app).