Inbox

The Gauzy Inbox brings together everything addressed to a user: questions, approvals, escalations and notices, with each user's own read, archive and snooze state. It is a general Gauzy feature and works without Ever Works; the Ever Works integration is its first source: questions and approvals of Ever Works agents land here, and a reply in Gauzy goes back to Ever Works and resumes the agent.

Switch it on

Turning it on grants, in every tenant, INBOX_VIEW, INBOX_MAILBOX_MANAGE and INBOX_MAILBOX_READ_ALL to the Super Admin and Admin roles, and INBOX_VIEW to Manager and Employee. With the email features off, every email still goes out over SMTP exactly as before.

Using the Inbox

Open Inbox (/pages/inbox); the bell in the header shows your unread count (read every minute, and at once after you change an item).

• Tabs: All, Decisions (open questions, approvals and escalations), Email, Notifications, Snoozed and Archived. Notifications are Gauzy's own employee notifications, shown here for the first time in the web app.
• Filters: kind, source, unread only, and text search.
• Question: pick one of the options (the recommended one is highlighted) or answer in your own words. When the question asks for a reason, the answer needs text.
• Approval: Approve or Reject, with a note.
• Escalation: what was tried, the decision needed and the confidence, with a note that resolves it.
• Notice: read-only.
• Per item: mark read or unread, archive or unarchive, snooze (an hour, until tomorrow, until next week, or wake it now), and open the linked task, project or agent.

Your read, archive and snooze state is yours alone: on an item shared by several people, each has their own.

Items from Ever Works

With the Ever Works integration on, the questions, approvals, escalations and notices Ever Works addresses to a person arrive in that person's Gauzy Inbox, linked to the task, project and agent they are about.

• An item reaches you only once your Ever Works account is paired with your Gauzy employee (Integrations → Ever Works → Mapping → People). Until then it waits and is tried again every hour, so it arrives within an hour of the pairing.
• Replies are sent at once, as you, and resume the agent's work in Ever Works. If the item was already decided in Ever Works, Gauzy says so and shows the answer Ever Works holds.
• Read / unread and archive follow to Ever Works; snoozing stays in Gauzy.

The integration also uses the Inbox for its own notices to the admin who connected it (source System):

• Needs re-authentication — the integration key was revoked or expired; enter a new one in the sync settings.
• Dead letter — a change could not be synced after repeated attempts; the notice names the latest record.

A repeat of the same notice updates it and marks it unread again rather than adding a new one.

Real time

When an item is created, the Inbox announces inbox_item.created on the platform's event stream. The event is addressed: the subscription surface delivers it only to the item's recipients, never to other users of the tenant. It carries the item's id, kind, source, status and priority — never its title, body or answer — so a client that hears about an item reads it through the Inbox API. GraphQL clients holding EVENT_OUTBOX_VIEW subscribe with subscription { events(names: ["inbox_item.created"]) { eventId data } }; a typed field for every Inbox user is planned. The web app keeps its one-minute badge refresh.

API

All routes are under /api/inbox and need INBOX_VIEW. The recipient is always the signed-in user, taken from the credential and never from a parameter.

See also

• Ever Works integration
• Email integration