> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kayanos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Home and notifications

> Configure a useful personal Home view, act on notifications safely, and understand the readiness conditions behind in-app, email, and device delivery.

Home is a personal operational workspace. It helps a member see the work that needs attention without turning a dashboard card or notification into the source of truth. Use Home to open the underlying task, request, event, file, or communication; make the accountable change on that underlying object.

In the Citizen Services Directorate scenario, a Registry Officer opens Home at the start of the day and sees an urgent completeness task for `CSR-2026-00042`, a scheduled inspection, unread work alerts, a quick service form, and a dashboard shortcut. The officer follows each item to its record before changing status or ownership.

## Goal

Create a focused Home layout, understand what a notification does and does not prove, and diagnose why a widget or delivery channel is unavailable.

## What Home can show

Home is a configurable grid. A member can enter edit mode, reposition widgets, add or remove supported widgets, adjust widget settings where available, save the layout, or reset it to the organization’s default layout. The product can filter visible widgets according to the member’s seat type, organization configuration, and available data, so not every member will see the same choices.

Common widget categories include:

| Widget category                  | Useful question it answers                                | Follow the item to                                           |
| -------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------ |
| Tasks and task metrics           | What is overdue, assigned, or awaiting me?                | The task and its related request/inspection                  |
| Calendar or events               | What appointment, review, or field visit is next?         | The calendar event and related service record                |
| Notifications                    | What changed that needs my attention?                     | The linked record, task, event, or communication             |
| Forms and shortcuts              | Which approved intake or staff action is used frequently? | The configured form or application route                     |
| Dashboards                       | What is the current workload or service trend?            | The affected queue or individual record before changing data |
| Chat, email, or recent documents | Which coordination or evidence item needs review?         | The conversation, mailbox item, or controlled file           |

Do not build a Home layout around a total count alone. A useful layout makes the next responsible action obvious: urgent work, today’s schedule, unread decision-critical notifications, and the fastest approved path to the underlying record.

## Distinguish Home from an application workspace

Home assembles your personal cross-organization work picture: assigned tasks, upcoming events, notifications, communication, and configured shortcuts. An application workspace is one level deeper. It organizes that application’s available pages by section and can show recently opened destinations plus live indicators that link to the relevant task, calendar, email, or chat view.

Use Home to decide what needs attention and an application workspace to choose the correct service destination. A live indicator, metric, or recent item is a navigation aid, not the authoritative count, status, or decision. Open its target, review the current filters and record state, and make the accountable change there.

The current Home experience is launcher-first. Search remains visible in the global header, while Home can combine the task summary, inline application browser, recent destinations, and personal starred shortcuts. The header also provides the currently available account, support, notification, language, and light/dark/system-theme controls. Changing language or theme changes the current member experience; it does not change organization content, permissions, or another member’s preference.

To manage shortcuts, open the application/launcher view and star an application, one of its pages, or an available utility. The Home shortcuts area updates from that personal list. Unstar an item to remove it. A missing shortcut usually means the destination was retired, the member changed organization, or current availability no longer permits it—not that the underlying permission should be broadened.

## Configure a focused Home layout

1. Open **Home** and identify the decisions you personally make during a normal service day.
2. Select the customize control to enter layout-editing mode.
3. Keep the essential widgets first: assigned/overdue tasks, the calendar preview, notifications, and any service-specific shortcuts you actually use.
4. Add a dashboard shortcut only when the dashboard leads to a defined review action. Do not use a dashboard card as the place to edit a citizen request.
5. Arrange widgets so high-priority work is visible without scrolling on the device used by the role.
6. Open widget settings where available and choose only approved data sources, filters, or shortcuts.
7. Save the layout. Use reset when the personal arrangement no longer supports the workday.
8. Test the layout as another role if that role has a different seat, scope, or daily responsibility.

**Expected result:** the Registry Officer can see the completeness task and today’s inspection at the start of the day, while the Field Inspector sees their own assigned work rather than the manager’s entire queue.

## Work from a notification

Notifications are prompts, not evidence. The production panel organizes them into two lanes: **Needs You** for personally directed or urgent work, and **Activity** for updates that normally do not require an immediate action. Repeated deliveries about the same underlying item are grouped into one thread, while **All** and **Unread** continue to control which loaded threads appear. Header and bell counts come from the full account totals rather than only the rows currently loaded.

The Home notifications widget uses the same classification. It shows Needs You threads within the widget's configured count and type filters, then reports how many Activity deliveries remain. Activity normally updates the badge without interrupting the member with a toast; Needs You events can still produce an in-app toast. A lane, badge, thread count, or toast is a triage signal—not a severity judgment or proof that the underlying work is still open.

Use this procedure for a service notification:

1. Open the notification panel and start with **Needs You**. Choose **Unread** when you are triaging only unseen work.
2. Read the thread title, actors, update count, and time. Select the row body to open its newest available target, or use the caret to expand the original deliveries without marking them read.
3. Check the record’s current status, owner, and scope. A notification can be older than the current state.
4. Perform the change on the underlying resource and leave an understandable activity/status update.
5. Confirm the notification read state. Opening a grouped row marks the delivery it opens, not every delivery in a long thread; reading never means the operational work is complete.
6. Mark all as read only after you have either acted, delegated, or deliberately recorded the next step for every item.

If a notification opens a target you cannot access, do not ask a colleague to copy the restricted data into chat. Ask the service owner to review whether the target’s scope and the recipient role were configured intentionally.

### Understand the AI-assisted summary

When the panel opens, deterministic lanes and threads remain usable while KayanOS may prepare a permission-scoped AI digest. If available, the digest can summarize the inbox, rewrite a Needs You title, or combine related Activity threads. AI-authored rows carry a visible marker, and the original deterministic notification titles remain shown beneath them; expand a row when you need the individual deliveries. The summary never grants access, changes read state, completes work, or replaces the source record.

If generation is pending, unavailable, or safely discarded by validation, the deterministic lanes remain the complete operating view and no AI banner is required. Do not wait for a digest before handling urgent work, and do not infer that a missing digest means there are no notifications.

## Triage support-ticket notifications

Support notifications lead to the ticket queue appropriate to the recipient. A requester who is an active organization member receives creation and requester-update events in **My tickets**. Members with organization support list/manage permissions can receive new-ticket and unassigned-reply events for their queue. Assigned support agents can receive assignment, assignment-change, customer-reply, and internal-note events. Handoffs notify the target assignee or eligible support team, while Kayan support SLA at-risk and breach events go to the responsible Kayan support scope.

Opening the notification uses a role-aware ticket link—for example, **My tickets**, the organization's internal/escalated queue, or the Kayan support queue—and the server checks current membership and ticket access again. The notification does not grant support-console access or expose a ticket outside the active organization. If an assignment or role changed after delivery, open the current queue and verify the assignee, routing state, status, priority, and latest conversation before replying.

When the ticket opener or linked requester replies from **My tickets**, KayanOS records a customer reply. A verified customer reply moves a ticket from **Waiting for customer**, **Resolved**, or **Closed** back to **In progress** and recalculates its support timing. This remains true when that requester also has organization support permissions. A reply from an organization or Kayan support console remains an agent reply, and an internal note never reopens the ticket. The server rejects customer reply context from anyone who is not the opener or linked requester; using **My tickets** does not grant access to another person's ticket.

Treat handoff and SLA-breach notifications as urgent routing signals. Their configured delivery can bypass quiet hours, while an at-risk warning can follow normal quiet-hours delay; channel readiness and current ticket access still apply. Do not mark a breach complete from the notification. Open the ticket, confirm whether the deadline is for first response or resolution, record the responsible action, and use the support workflow's current state as the source of truth.

## Delivery readiness and preferences

The presence of a notification preference does not guarantee delivery through every channel. Effective settings can come from the notification catalog, organization policy, and a member-specific override. Delivery also depends on the channel being ready.

| Channel                      | What the member can expect                                                   | Readiness conditions to explain                                                     |
| ---------------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| In-app                       | The item appears in the KayanOS notification experience when it is delivered | The member is signed in or later opens the app; target access remains separate      |
| Email                        | An organization-approved notification email can be sent when enabled         | The member needs a usable email address and the address must not be suppressed      |
| Push                         | A device notification can be attempted when enabled                          | A registered device and granted device/browser notification permission are required |
| Optional configured channels | Availability follows the organization’s published configuration and policy   | Required contact data, consent, and channel-specific readiness must be met          |

Quiet hours are a member setting with timezone, start, and end time. For channels other than in-app, an enabled quiet-hours policy can delay delivery until the next allowed time unless the organization defines a bypass for the notification’s priority. Explain this as a delivery policy, not as a reason to ignore urgent work already visible in Home.

## Availability and permissions

Any signed-in member can have a Home route, but individual widgets and their linked actions depend on configuration, seat, data availability, and access. A Home card does not override the list/open/update/share/delete verbs of the record it points to.

Before escalating an “empty Home” issue, check:

1. Is the member in the correct organization?
2. Does the member have assigned work, events, notifications, forms, dashboards, or files that the widget can show?
3. Is the widget allowed for the member’s seat and organization configuration?
4. Does the member have access to the target resource, not only the Home shortcut?
5. Is a notification channel ready and enabled at catalog, organization, and member levels?

## Safe testing

Use one controlled request and two different roles. Give the Registry Officer one action-required event plus several Activity updates on the same synthetic item. Confirm that the panel separates the lanes, groups the repeated updates, expands to the originals, and keeps Activity arrivals silent while updating the badge. If an AI digest appears, confirm that every rewritten or clustered row still shows its original titles and opens only a target the member may access. With a synthetic support ticket, verify that the requester link opens **My tickets**, an eligible support member reaches only the appropriate queue, and a non-recipient gains no access from the copied route. Resolve the synthetic ticket, reply as its requester from **My tickets**, and confirm it returns to **In progress**; then confirm an agent reply and internal note from the support console do not reopen it. Change one member notification preference and verify the in-app behavior without relying on a real citizen or external delivery. Test quiet hours only with approved non-production timing and record the observed result.

## Troubleshooting

| Symptom                                                           | Likely cause                                                                                                       | Safe response                                                                                                                                                                                                     |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A widget is missing                                               | It may be unavailable for the member’s seat, configuration, or data                                                | Confirm availability before asking for a broader role                                                                                                                                                             |
| A widget is empty                                                 | There is no matching assigned work, event, record, or accessible data                                              | Open the underlying queue and verify filters/assignments                                                                                                                                                          |
| A notification is marked read but work remains                    | Reading/opening is separate from completing the task                                                               | Open the target and record the actual next step                                                                                                                                                                   |
| A thread opens only its newest update                             | A grouped row is a triage shortcut, not the full activity history                                                  | Expand the caret for loaded originals, then use the underlying record's activity/history view for the authoritative sequence                                                                                      |
| Only the most recent notification threads are shown               | The grouped panel holds a bounded recent set and states when more threads exist                                    | Open the source queues and records for older work; do not treat the panel as a retention archive                                                                                                                  |
| An AI digest is missing or still loading                          | The inbox may be empty, generation may be pending/unavailable, or validation may have kept only deterministic rows | Continue from Needs You and Activity; do not retry repeatedly or treat the digest as required evidence                                                                                                            |
| A support notification opens an unavailable ticket or wrong queue | The active organization, ticket routing/assignment, or current support permission changed after delivery           | Return to Support, open an allowed queue, and ask the support owner to review the narrow assignment/permission; do not share the ticket contents                                                                  |
| An expected support update did not arrive                         | The member is not the requester/assignee/eligible support recipient, or the chosen channel is not ready            | Check the live ticket and recipient role first, then test in-app delivery before changing channel or role policy                                                                                                  |
| A completed support ticket did not reopen after a reply           | The reply came from a support console/internal note, or the member is not the ticket opener or linked requester    | Open the ticket through the requester's **My tickets** view and send a genuine customer reply. Do not change status merely to compensate for an agent note; route ownership/access problems to the support owner. |
| Push notification did not arrive                                  | Device, permission, preference, or quiet-hours readiness is missing                                                | Check the member’s channel readiness and test in-app first                                                                                                                                                        |
| A dashboard number looks wrong                                    | The widget is a summary, possibly filtered or delayed                                                              | Open the source queue and inspect the individual records                                                                                                                                                          |
| A workspace insight and source queue differ                       | The insight is a compact navigation summary and the source may have newer state or different filters               | Open the linked queue, confirm filters, and use the underlying records                                                                                                                                            |
| “Mark all read” hid important work                                | Read state was used as a completion signal                                                                         | Re-open the task list and create/assign an explicit follow-up task                                                                                                                                                |

## Related guides

* Manage accountable follow-up in [Tasks and approvals](/work/tasks-and-approvals).
* Schedule the next service action in [Calendar](/work/calendar).
* Configure personal notification and language settings in [Profile, language, and signatures](/work/profile-language-and-signatures).
* Understand access boundaries in [Roles and access](/start/roles-and-access) and [Permissions and availability](/reference/permissions-and-availability).

![KayanOS home and notification view for a representative citizen-service queue.](https://kayanos.app/docs-images/en/work/home-and-notifications.png)