Agents are useful because they can do things: look up a record, send a message, open a pull request. Approvals are how you keep that from happening blindly. Notifications are where those requests land, along with mentions, Jam invites, and finished runs.
You don't need a separate admin console for everyday review: most of it happens in the thread and under Notifications in the left icon strip.
Ask first vs automatic
On each project, Tools lets you choose how integrations behave:
- Ask first: the agent proposes the action and waits. You see a card in the chat and in Notifications.
- Automatic: the agent may use the tool as part of the task, still leaving an artifact you can inspect.
Ask first is the right default for anything that emails a customer, writes to a CRM, deploys, or spends money. Automatic is fine for read-only lookup once you trust the connection.
Review an approval
When an agent needs permission:
- Open the card in the thread, or go to Notifications.
- Read what it wants to do and which tool it will use.
- Approve, decline, or set a custom status if your workspace uses one.
Declining stops that action. The agent can continue the conversation with a different approach if you tell it to.
Task-style approvals (when someone asks you to sign off on a piece of work) use the same idea. You'll still see them in Notifications rather than hunting a hidden queue.
What else shows up in Notifications
Besides tool approvals:
- Mentions in topics, DMs, and project agent threads
- Agent runs that finished or need you
- Jam invites
- Other workspace activity your notification preferences allow
Mark items read as you go. On the desktop app, notifications can also appear in the tray so you don't have to keep the tab focused.
Preferences
Under Settings you can tune which events you hear about. Workspace-wide audit history (who approved what) lives with admins in Settings & billing. For how Kluff thinks about least-privilege tools and artifacts, see Security.

