Attribution travels with the message
A notification carries the identity of the system or agent that raised it and the tenant it belongs to.
PlatformAgentLabs Notify
When an action needs a person to hear about it.
AgentLabs Notify is the multitenant notification foundation for AgentLabs systems. Applications submit intent; Notify owns routing, durable delivery, receipts, and the record of what was sent, to whom, and on whose authority.
AgentLabs Notify
- Delivery
- Sent once, even when systems retry.
- Attribution
- Every message carries its sender.
- System events
- Approvals and alerts reach the right people.
Where it stands
AgentLabs Notify is at foundation stage. Email delivery exists; other channels are planned. It is not a release.
Where it is heading
Direction, not shipped capability
Further channels, templates, tenant-managed integrations, and webhooks, and maturing from shared infrastructure into a separately consumable product.
What it does
Sent once, attributed always.
- Only known systems can send. Every submission carries its own workload credential from Auth, never a borrowed one.
- A notification goes out once, even when systems retry, and its payload stays encrypted at rest.
- Email delivery with normalised retry, terminal, and reconcile outcomes, and receipt lookup.
- Tenant isolation in the database and fail-closed fencing tied to Auth's application lifecycle.
What makes it agent-era
The message carries its sender's identity.
Approvals and receipts as events
Approval requests, receipts, and alerts from agent activity reach people through the same governed path.
The next step
Talk with AgentLabs about AgentLabs Notify.
Bring your identity, policy, and evidence requirements. We will say plainly what is verified and what is not.