Notifications & My Work

My Work combines a user's active work and targeted operational notifications in the sidebar and on a paginated history page.

My Work

The sidebar is the compact view of items that currently need the signed-in user's attention.

• Pinned session actions and bots provide quick launch.
• Active sessions, draft plans, and active round tables link to ongoing work.
• Unread and starred notifications surface alerts.
• Tickets appear when you are the assigned QA reviewer in QA Approval, or the assigned developer for a Pull Request with merge conflicts. They update automatically when assignment, stage, or conflict status changes.
• The My Work page provides filtering, pagination, and completed history across item types.

Use Hide to remove a session, plan, or round table from My Work without deleting the underlying record. Use Dismiss on a notification to hide it from the sidebar; it remains available in My Work until retention removes it. Bulk hide operations require confirmation.

Notification lifecycle

Notifications are stored per recipient, including when that user is offline.

1. Open a notification to mark it read and view its full message.
2. Use the action button, when present, to open the related session, ticket, merge, or other resource.
3. Star an item that must remain prominent and survive automatic retention.
4. Dismiss it when no longer needed in the sidebar.

A notification does not grant access to its linked resource. If access was removed after delivery, the link can be unavailable even though the notification remains.

Recipients

Operational notifications are targeted to responsible users rather than every signed-in user.

Condition	Typical recipients
Session checks, hooks, workflows, or verification fail	Session owner and, for ticket work, the assigned developer.
Ticket implementation or review needs attention	Ticket creator, assigned developer, or assigned QA reviewer as applicable.
Merge fails	Merge initiator and responsible ticket user.
Automation fails or is disabled	Automation owner and responsible session or ticket users where applicable.
Budget approaches or reaches a limit	Administrators for global budgets; relevant workspace members for workspace or task budgets.
Host credential expires, is revoked or rotated, or has suspicious failures	Administrators and users permitted to manage host API keys.
License approaches expiry	Administrators.

Administrators can receive installation-wide operational alerts. Keep role assignments and ticket ownership current so alerts reach the correct people.

Browser notifications

Browser notifications provide a local desktop alert while the Polygent tab is in the background.

1. Open Profile → Notifications.
2. Enable browser notifications.
3. Approve the browser permission prompt.
4. Allow notifications for the site in browser and operating-system settings.
5. Select Send test notification to verify local browser delivery.

The preference is per user and off by default. Delivery requires a signed-in browser session and an open Polygent page; it is not a mobile push or email service. Shared or sensitive workstations should leave browser notifications disabled because titles or message text may appear on the lock screen.

Retention

Automatic retention prevents the inbox from growing indefinitely.

Notification state	Retention
Read and unstarred	Removed after 30 days.
Unread and unstarred	Removed after 90 days.
Starred	Retained until unstarred and then eligible for normal cleanup.

Retention deletes the notification only, not the linked ticket, session, or other source record. Star alerts that must remain in the application, and use an external incident or audit system for durable compliance records.

Troubleshooting

Notification delivery depends on recipient assignment, access scope, browser state, and retention.

Symptom	Resolution
Expected notification was not received	Verify the user was the owner, assignee, reviewer, workspace member, or privileged operator when the event occurred.
Linked item cannot be opened	Confirm the resource still exists and the user still has its permission and workspace membership.
Sidebar item disappeared	Check the full My Work history and filters; it may be read, dismissed, hidden, completed, or removed by retention.
Browser notification does not appear	Enable the Profile preference, grant site and OS permission, keep a signed-in tab open, select Send test notification, and test while the tab is hidden.
Browser permission was denied	Reset notification permission for the Polygent site in browser settings, reload, and enable it again.
Too many alerts	Correct stale ownership and assignments, resolve repeated failures, and dismiss completed alerts rather than disabling operational monitoring.

See Profile for the user setting and AI Cost Budgets for budget-alert behavior.