> For the complete documentation index, see [llms.txt](https://docs.cubilock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubilock.com/profile-management/privacy-settings/personal-apps-work-notification.md).

# Personal Apps Work Notification

**Personal Apps Work Notification** lets administrators control which **personal apps** are allowed to **read work profile notifications** using Android’s `NotificationListenerService`. By default, apps in the personal profile cannot receive or read notifications generated by work profile apps unless explicitly allowed. This policy setting lets you selectively permit trusted personal apps to read those work notifications.

#### Navigation:

Device Management → Device Profiles → Edit Profile → Privacy Settings → Personal Apps Work Notification

#### **What This Setting Controls**

Android separates work profiles from personal profiles on the same device to protect corporate data and user privacy. Work profile notifications (such as messages from a corporate email app or reminders from a work calendar) are delivered separately from personal app notifications.

By default:

* **No personal apps** (aside from Android system apps) can listen for notifications generated by work profile apps.
* Work notifications are isolated from the personal profile by design for security and privacy reasons.

The `Personal Apps Work Notification` section allows you to add specific personal apps that are permitted to read work notifications using a `NotificationListenerService`. This can be useful for scenarios such as:

* Allowing a personal productivity app to consolidate notifications from work apps.
* Supporting wearable or companion apps that must display or act on work notifications.
* Enabling third‑party notification managers that require access to work profile notifications.

#### **How to Configure Personal Apps Work Notification**

1. **Open the Personal Apps Work Notification section** in the Privacy Settings tab.\
   You will see an empty list if no apps are added yet.

<figure><img src="/files/GxOpHkwBLMP71OlT57SP" alt=""><figcaption></figcaption></figure>

2. Click **Add Application** to open a searchable list of installed apps (both system and user‑installed).

<figure><img src="/files/gr3YdAIdmkBRpVprsycK" alt=""><figcaption></figcaption></figure>

3. In the **Add Application** dialog:

* Search for and select the personal app(s) that you want to allow to read work profile notifications.
* Check the box next to the app name.
* Click **Add** to include it in the list.

4. After adding the desired apps, click **Save** in the profile editor to apply these changes to the devices.

<figure><img src="/files/c4oh5qjfsKB88LeP16ED" alt=""><figcaption></figcaption></figure>

Once saved, the selected personal app(s) will be allowed to use Android’s `NotificationListenerService` to monitor and read notifications coming from work profile apps, while still respecting Android’s notification access permissions.

#### **On‑Device Behavior**

* Only the personal apps you explicitly add here will receive callbacks for work profile notifications via a notification listener.
* Other personal apps will not have access to work profile notifications, preserving separation between personal and corporate data streams.
* Devices enforce this at the OS level; developers cannot bypass this restriction without this configured allowlist.

#### **Best Practices & Considerations**

* **Minimize the number of personal apps allowed** to read work profile notifications — only add trusted apps.
* Ask app developers to use professional NotificationListenerService best practices to avoid privacy leakage and unnecessary access.
* Ensure users understand that enabling a personal app to read work notifications means that sensitive work notification content might be available to that app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cubilock.com/profile-management/privacy-settings/personal-apps-work-notification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
