Approval decisions
LiveEvery action that writes outside your workspace passes through the approvals queue. What was proposed, who approved or rejected it, and when, is recorded.
When AI does work for clients, someone eventually asks what it did. Riley keeps an honest record: approval decisions, signed receipts, and per-key access. Here is exactly what is recorded today, and what is still rolling out.
approvals · signed receipts · per-key access
Start freeEvery action that writes outside your workspace passes through the approvals queue. What was proposed, who approved or rejected it, and when, is recorded.
Completed work is assembled into signed, chained receipts with a public verify link. That is a record you can hand to a client or a manager and they can check it themselves.
Each AI surface connects with its own per-workspace key. You can see which keys exist and when each was last used, and revoke any of them from Settings.
A per-surface breakdown of which AI client asked for what, over time, in one view. This is rolling out and is labeled coming soon everywhere until it ships.
When you run AI on behalf of clients, or across a team, the hard part is not doing the work: it is showing what was done and that a person stood behind the ones that mattered. A record of approval decisions answers who signed off. Signed receipts answer what actually happened. Per-key access answers which surface did it and when. That is the difference between saying the AI helped and being able to prove exactly what it did.