Skip to main content

Notifications & My Work

Polygent keeps everything you personally need to act on in one place. The My Work surface in the sidebar merges your active sessions, draft plans, active round tables, and notifications into a single live list, and the inbox delivers targeted alerts — a failed hook, a ticket waiting on your approval, a budget warning — to the people actually responsible, never to the whole workspace.

My Work​

My Work is the top section of the sidebar. It shows, in one merged and live-updating list:

  • Quick-launch row — your pinned actions and bots, one click to start
  • Active sessions — Chat, Develop, and Bot sessions in progress
  • Draft plans — plans still moving through the wizard
  • Active round tables — open deliberations
  • Notifications — your unread and starred inbox items

Everything updates automatically as work progresses — no refresh. The full history (including completed items) lives on the My Work page at /my-work, a single table spanning all four types with filtering and pagination.

Managing items in My Work​

  • Star a notification to pin it to the top of the list.
  • Dismiss an item to hide it from the sidebar (it stays in the /my-work history table).
  • Hide sessions, plans, and round tables individually or in bulk to declutter.

The inbox​

Notifications are persisted when they happen, so you'll see them on your next sign-in even if you were offline. Each notification has a title, a body, and — when relevant — a deep-link button that takes you straight to the source (for example, Open Session or Open Ticket).

Clicking a notification opens its detail page, marks it read, and shows the action button when there's somewhere to go. System notices with no linked entity simply show the message.

Who gets notified​

Notifications are targeted, not broadcast. Polygent sends each alert only to the people responsible for the event:

EventGoes to
Code review found blocking issuesThe ticket's assigned developer, otherwise the session owner
Hook failedThe ticket's assigned developer, otherwise the session owner
Ticket failedThe ticket creator and assigned developer
Workflow step failedThe session owner and the ticket's assigned developer
Verification failedThe session owner and the ticket's assigned developer
Merge failedThe merge creator and the ticket's assigned developer
Automation failed / auto-disabledThe automation creator (plus session owner/developer when a session was created)
Budget warning or breachAdmins (global) or workspace members (workspace/task)
Host API key expiring, expired, revoked, rotated, or showing suspicious auth failuresAdmins and anyone who manages host API keys

Admins always receive notifications for workspaces they oversee, even without an explicit membership row.

Browser push​

Opt in to browser push from Profile → Notifications. When the tab is hidden and a notification arrives, Polygent surfaces it through your browser's native notifications; clicking it jumps to the deep link. This is per-user and off by default.

Retention​

The inbox tidies itself automatically:

  • Read, un-starred notifications are removed after 30 days.
  • Any un-starred notification is removed after 90 days, read or not.
  • Starred notifications are kept indefinitely — star anything you want to keep.

Examples​

Approval routing without a standup A developer queues a ticket and assigns QA. When implementation finishes, only the assigned developer is notified that it's ready for review; after they approve, only the QA reviewer is notified. No one wades through alerts that aren't theirs.

Catch a broken pipeline fast A workspace's on-done hook runs the test suite. When it fails on a ticket session, the ticket's assigned developer gets an inbox notification (and a browser push if their tab is in the background) with a one-click link back to the session — so the failure is seen in minutes, not at the next check-in.

Keep an eye on spend With a workspace budget set, the workspace members get a single inbox warning at 80% of the monthly cap and a clear breach notice if it's reached — surfaced right next to their active work in My Work.

Pin what matters A team lead stars the "license expiring in 7 days" notification so it stays pinned at the top of My Work until they've uploaded the renewal, instead of letting it scroll away.

See Also​