> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/how-to-guides/configure-app-audience-and-notification-prefs.md).

# Configure App Audience and Notification Prefs

App-level **audience policy** keeps Work Queues and Decisions isolated by company (tenant) and role, and lets Notification Center honor category preferences.

{% hint style="info" %}
**Shipped 9 Aug 2026**\
Part of the guided Automation maker controls in the [9 Aug 2026 Release](https://docs.notionapps.com/release-notes/9-aug-2026-release).
{% endhint %}

## When to use this

* Two client companies must never see each other’s review items.
* Sales Reps and Managers need different queues.
* Users should opt into review alerts via a checkbox on their user profile.

## Prerequisites

* Private OTP app with a Users sheet.
* A **Role** field (select / multi-select).
* Optional **Client** (or Company) relation for tenancy.
* Automation screens (Work Queue / Decision / Notification Center) available.

## Steps

### 1. Open audience policy

On any Automation screen, open **App audience & notification prefs** (or the equivalent Automation Home control).

### 2. Tenant mode

1. Choose **Relation** when each user belongs to one client/company.
2. Pick the users-sheet **Client** (or equivalent) relation.
3. Save.

Workflow role-pool routing still assigns by role; tenant policy filters which company’s items appear for that role.

### 3. Role field

Leave auto-detect or explicitly pick the **Role** field used by Screen Visibility and role-pool publish steps.

### 4. Notification categories

1. Add a category key (for example `reviews`).
2. Bind it to a boolean on the users sheet (for example **Alert Reviews**).
3. Wire Messaging / workflow notify steps to that category so Notification Center and email honor the preference.

### 5. Verify

1. Publish.
2. Log in as two users in different companies with the same role — each should only see their company’s queue items.
3. Turn a preference off and confirm that category no longer delivers in-app (or email, depending on channel).

## Related

* [Work Queue Screen](https://docs.notionapps.com/screens-and-components/types-of-screens/native-automation-and-operational-screen-guides/work-queue-screen)
* [Decision Screen](https://docs.notionapps.com/screens-and-components/types-of-screens/native-automation-and-operational-screen-guides/decision-screen)
* [Client Review Hub in 15 Minutes](https://docs.notionapps.com/guides/client-review-hub-in-15-minutes)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/how-to-guides/configure-app-audience-and-notification-prefs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.