Relays are built so that a person stays accountable for everything a Relay does.
Acts on behalf of a person
Every job runs on behalf of the person who delegated it — the job shows this as Runs on behalf of. The Relay uses that person's access, checked again each time it reads or acts. It can never see or do more than that person could, and a handoff to another Relay never adds access.
Never impersonates
A Relay always has a robot avatar, never a photo or initials, and is always labelled AI Relay — on jobs it shows as "Accountable: [Relay name] (AI Relay)". Emails and invites are sent through the account you chose in setup, after a person approves the exact content.
Approval for anything outside
Sending email and booking, moving, or cancelling meetings always need approval. Saving to the Library, handing work off, changes in connected tools, running workflows, and browser or computer actions that change something outside need approval depending on the permission preset. Anything a preset allows that changes something is checked by auto-review first, which sends it to a person when something looks off. Approvals cover the exact content shown, expire, and are re-checked before the action runs. See Jobs and approvals.
Audit trail
The Relay's Log (under More) is read from the workspace audit log. Equipment actions are recorded under the delegating person, with the Relay named as the agent. Jobs keep their evidence, their tool calls, the version of the Relay they ran on, and the decisions made on each review.
Who can change a Relay
Only the Relay's owner, its steward, or a workspace admin can edit, pause, or retire it. Workspace admins can stop every Relay at once with Emergency pause in the Governance view of the Relays page. Retiring keeps a Relay's jobs, versions, and log.
Billing
Model usage for a Relay's jobs, chat updates, and routines is billed to the person who delegated the work. File knowledge is billed like any other knowledge base. See Costs.