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

# Custom visibility for apps

> Dynamically control which clients can access an app.

With custom visibility for apps, you can dynamically control which clients have access to an app. This lets you provide differentiated levels of service to clients. For example, you might only allow clients with the custom field **plan = premium** to schedule time with you (access to the [Calendly app](/docs/embeds-and-links/calendly)) and message you (access to the [Messages app](/docs/built-in-apps/messages)).

You can configure which clients can see an app by selecting clients and companies directly, or you can use [custom field rules](/docs/core-concepts/custom-fields).

Since custom fields are supported on Zapier, Make, and our API, you can change custom app visibility via [automations](/docs/advanced-features/automations-introduction). For example, you could set up a workflow in Zapier where the custom field **plan** is updated from **standard** to **premium** only after a particular contract is signed.

## How to access custom visibility rule settings

1. Click **App Library** in the sidebar, then click **Edit** next to the app you want to set visibility rules for to access the app's settings page.
2. Scroll to the bottom of the app's settings page and click **Edit** under **App Visibility**.
3. A modal appears allowing you to configure visibility rules. You can select **Visible to everyone**, **Visible to no clients**, or **Custom visibility**.

## Custom visibility rule options

If you select **Custom visibility**, you can configure granular controls for which clients can access the app.

The **Show if** dropdown displays Clients, Companies, and a list of your client and company custom fields.

<Note>
  Only client and company **Tags** custom fields are configurable for custom visibility rules. Other custom field types will not be displayed here.
</Note>

| Rule type     | Configuration                                                                                                                                    |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Clients       | Select which individual clients will have access to the app.                                                                                     |
| Companies     | Select which companies will have access to the app. All clients who belong to the included companies will be able to access the app.             |
| Custom fields | For any **Tag**-type client or company custom field, you can grant access to the app based on three conditions. See the table below for details. |

| Custom field condition          | Details                                                                                                                                                                                                                                |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Includes (Includes any of)      | Grants access to the app if the client has a specific tag or tags. If multiple tags are selected, this property changes to **Includes any of**, and any client with any selected tag will have access to the app.                      |
| Is not (Doesn't include any of) | Grants access to the app if the client does not have a specific tag or tags. If multiple tags are selected, this property changes to **Doesn't include any of**, and any client with any selected tag will not have access to the app. |
| Includes all of                 | Grants access to the app only if the client has all of the selected tags.                                                                                                                                                              |

### Add an OR rule

You can add additional OR rules for custom visibility, which allows for additional configuration.

For example, you can set up a rule where a **Tags** field includes "Tier 1" or a **Company** includes "Company A". This grants access to all clients with the "Tier 1" tag, as well as all clients belonging to "Company A", regardless of the tags for clients in that company.