Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers · Soon
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
Help Center
🔔

Notifications

Found this helpful? Share it:

Notifications keep you in the loop when something needs your attention: a mention, a shared resource, a workspace invite, a billing alert, or a message from an agent or automation 🔔

What you get notified about

  • Agents and automations: an agent or an automation you set up pings you when a job finishes or needs a decision.

  • Workspace activity: invitations, shares, mentions, and broadcasts from members of your workspaces.

  • Computers and jobs: hibernation, workflow errors, budget warnings, and auto-termination.

  • Billing: usage thresholds, a low credit balance, and auto top-up confirmations.

  • Support: replies to your support tickets.

Delivery channels

Every notification type can reach you on up to three channels. Control each channel per type in Settings → Notifications.

  • In-app: the bell in the sidebar, always on for routine events.

  • Email: sent to the address on your account, best for things you need to see while offline.

  • Web push: system push on supported browsers and phones, enabled once per device.

When another member, an agent, or the API tries to reach you on a channel you turned off, your choice wins and that channel is skipped. Account-critical messages such as billing receipts and security alerts are the exception, because they always reach you on the channels they need.

Quiet hours

Set a daily window when email and web push go silent while the in-app inbox keeps working. Pick a timezone so the window follows your location rather than UTC.

A few time-critical alerts still come through during quiet hours: a computer's auto-termination, a usage warning at 90 percent of a limit, and a computer workflow error. Everything else waits until the window ends.

Read and archive

Click a notification to open it and mark it read. Use Mark all as read to clear the unread badge in one step. Archive a notification to file it away without it counting toward your unread count.

Deep links and action buttons

Most notifications carry a deep link: clicking one in the bell, an email, or a push takes you straight to the chat, file, workspace, computer, or billing page it is about.

Some also offer action buttons, such as Accept or Reject on an invitation. These run a single action and skip the trip through the app. They work the same in the bell, in email, and in push actions on supported platforms.

Links carry no secret access token, so they need your normal signed-in session. If you open an emailed invitation while signed out, the button takes you through the usual sign-in and then to the destination.

Notifications from agents and the API

An agent with the notifications permission can ping you when a task finishes. It cannot override the channels you turned off, and sends are capped at 100 per 24 hours per sender. A single message to several people counts as one send. Revoke the permission in the agent's settings to stop future sends.

The same limits apply to notifications sent through the API or CLI.

Related articles

📊

Plans, allowances, and credits

How the free daily allowance, subscription plans, and Usage Credits fit together, and what happens when you reach a limit.

🔗

Sharing and access control

Share files, folders, and chats with a link, and understand who can see or change what.

🔔

Notifications API

Send notifications to workspace members and manage your inbox programmatically.

🔔

Notifications from the CLI

Read your inbox and notify workspace members with idapt notification.

🔔

Agent notifications

Let agents ping you when a long task finishes or needs a decision.

Up next

Your data and privacy

What idapt stores, who can see it, how AI providers handle it, and the controls that keep you in charge.

Was this helpful?