One admin consent grants Aristo six Microsoft Graph read permissions across your organization; for a person who uses Aristo, it can also read their mail and calendar and send mail as them, only when they ask. Leaders see only teams of 5 or more, and Aristo never trains on your data — SOC 2 is in progress, stated plainly.
8 more permissions are opt-in, 5 of them writes. Seat moves use separate license-only consent; extended capabilities use extended consent.
Organization-wide reads. Aggregate. Revocable.
One admin consent grants Aristo six Microsoft Graph read permissions across your organization; for a person who uses Aristo, it can also read their mail and calendar and send mail as them, only when they ask.
Everything Aristo reads, why, and its real grant state — the whole security review on one page. Nothing is installed server-side in your tenant; consent is one click by your admin in Microsoft Entra, and revocable there at any time. States shown reflect your tenant the moment it connects.
The exact access — and its real state
The extended consent grants its whole set together.
Sign in · Review and grant the admin consent →
Requires a Global Administrator. Entra shows every permission before anything is granted. This one click grants the whole registration, Mail.Send (delegated) included — a send on a person’s own press, not a read.
Supported environments
| Environment | State | Plainly |
|---|---|---|
| Microsoft 365 commercial cloud | supported today | The Graph usage-report surfaces Aristo reads are fully available. |
| Display-name concealment tenants | supported — counted mode | Your privacy setting is honored: seats ready to activate are COUNTED but never individually reached. |
| Multi-geo tenants | supported | Aggregate Graph reads work across geos. |
| GCC / GCC-High / DoD | roadmap | Government-cloud report APIs differ — we say so honestly rather than half-work. Ask us before piloting there. |
Actions and privacy boundaries
- Two kinds of write exist, and both are named: the extended consent’s application writes, off until your admin grants that consent and audited when used, and delegated
Mail.Send, which sends YOUR draft only on YOUR press. Everything else Aristo emits is a Teams message, or one of the three operational e-mails the trust page names. - Actions on your behalf require your own press. With admin consent, Aristo also acts as the app: Teams messages, the weekly sponsor digest, and a seat move after a leader approves it. Three operational emails are sent as the app: an enabled consumption signal to a named account contact, a sandbox-access notice, and a return-consent challenge. Named department views follow the organization’s visibility policy, each person’s naming choice and the five-person floor; personal activity stays private.
- Leader measures describe teams of five or more. The single exception is a named department view under your organization’s named-data contract. Eligible people are included by default unless a privacy exclusion applies; earlier “do not name me” choices remain honored. The five-person floor still applies, and the view shows only a name and cohort membership—never a personal activity ledger, prompts, documents, timeline, or usage ranking.
- Never estimate — anything unmeasured is shown as missing, with the exact consent that would light it up.
- Never train on your data — your tenant's signals compose your report, nothing else.
The note to IT — ready to paste
Forward this as-is; it carries the access list, the posture, and the consent link.
A person answers within one business day — email us · or say help, stop, resume or tip to Aristo in Teams.