## Custom Visibility for Apps

How to set custom visibility for your apps.

### Overview

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 custom field **plan = premium** access to schedule time with you (e.g. access to the [Calendly App](/content/apps/directory/calendly-app/index.html)) and message you (e.g. access to our [Messages App](/content/apps/directory/messaging-app/index.html)).

You can configure which clients can see an app by selecting clients/companies directly, or you can make use of [custom field rules](/content/guide/custom-fields/index.html).

Since we support custom fields on Zapier, Make, and our API, this makes it possible to change custom app visibility via [automations](/content/guide/intro-to-automations/index.html). 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.

### Learn how to set custom visibility for your Apps.

### How to access custom visibility rule settings

1. Click _App Setup_ 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 will appear 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’ll be able to configure granular controls for which clients can access the app.

| 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 will be able to grant access to the app based on 3 conditions. See the table below for more details. |

| Custom Field Condition | Details |
| --- | --- |
| Includes (Includes any of) | Grants access to the app if the client has a specific tag or tags. <br>If multiple tags are selected, this property will change 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. <br>If multiple tags are selected, this property will change 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 would grant 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.