Meet Luna. She handles your identity work for you.

She reads the request, gathers the context, and routes the approval to the right person — in Slack, where they already are. Time-boxed grants land with their expiry attached.

She reads every grant before the reviewer does and recommends the decision with the evidence attached. Reviewers confirm; she executes and records.

Joiners land with day-one access, movers get re-decided rather than accumulated, leavers are fully closed — she runs the flows and chases whatever blocks them.

She works the findings queue down: dormant accounts, standing access, agents without owners — each one driven to done, not parked in a dashboard.

Your runbook on triggers: when the event fires, she runs every step, chases what blocks it, and records what happened.

Everything she does lands in the record as she does it — decisions, revocations, certificates. The audit that starts this morning finds the file already made.

Observer reads and analyses: no writes, no actions. Supervised requires confirmation for everything. Custom is fine-grained: you set the rules.

Every tool Luna can use, from provisioning to revocation to outreach, carries its own verdict. There is no blanket trust.

Destructive actions can be hard-blocked. Luna cannot use them, no matter what the job asks for.

Needs Approval keeps a person in the loop: Luna proposes the action, shows her reasoning, and waits for a yes.

A Guarded action auto-approves only when one of your rules matches, written against real dimensions like member, resource and access. Otherwise it asks.

Org defaults cascade to automations, agents, and single chats. Overrides are visible and revertible, and you hear about what she does the moment she does it.