# Access Settings

**For the following shortcodes:**

* **`[in_email_domain_list]`**
* **`[not_in_email_domain_list]`**
* **`[in_email_list]`**
* **`[not_in_email_list]`**

Please read [our documentation on Email Lists](/publishing/control-access/email-lists.md) for further details.

They also all need the parameters `lists="???, ???"` with the IDs of the created Email List.&#x20;

***

**For the following shortcodes:**

* **\[subscriber]**
* **\[not\_subscriber]**

Need the `content_id="???"` with the ID of the event in the shortcode in order to work.

The `attendance_mode` parameter is also accepted and specifies the attendance mode a user needs to have in order to see the content between the shortcode.&#x20;

**Details:**

* **Type**: Text
* **Default Value**: *None*
* **Usage**:&#x20;
  * `attendance_mode="remote"`&#x20;
  * `attendance_mode="in_person"`

***

**\[guest]**

Displays content only to users who are not logged in.

* **Usage**:

```
[guest]
    Content for guests only.
[/guest]
```

***

**\[logged\_in]**

Displays content only to logged-in users.

* **Usage**:

```
[logged_in]
    Content for logged-in users.
[/logged_in]
```

***

**\[subscriber]**

Displays content only to users with an active subscription.

* **Usage**:

```
[subscriber content_id="123"]
    Content for subscribers only.
[/subscriber]
```

***

**\[not\_subscriber]**

Displays content only to users without an active subscription.

* **Usage**:

```
[not_subscriber content_id="123"]
    Content for non-subscribers.
[/not_subscriber]
```

***

**\[email\_domain\_allow]**

Displays content to users whose email domain is explicitly allowed.

* **Parameters**:
  * **domain** *(optional)*: Specify a comma-separated list of allowed domains.
* **Usage**:

```
[email_domain_allow domain="example.com,anotherdomain.com"]
    Content for specific email domains.
[/email_domain_allow]
```

***

**\[email\_domain\_not\_allowed]**

Displays content to users whose email domain is not in the allowed list.

* **Parameters**:
  * **domain** *(optional)*: Specify a comma-separated list of disallowed domains.
* **Usage**:

```
[email_domain_not_allowed domain="restricted.com,blockeddomain.com"]
    Content restricted by email domains.
[/email_domain_not_allowed]
```

***

**\[in\_email\_domain\_list]**

Displays content if the user's email domain is in a predefined list.

* **Usage**:

```
[in_email_domain_list]
    Content for users in the email domain list.
[/in_email_domain_list]
```

***

**\[not\_in\_email\_domain\_list]**

Displays content if the user's email domain is **not** in a predefined list.

* **Usage**:

```
[not_in_email_domain_list]
    Content for users not in the email domain list.
[/not_in_email_domain_list]
```

***

**\[in\_email\_list]**

Displays content if the user's email is explicitly in a predefined list.

* **Usage**:

```
[in_email_list]
    Content for users in the email list.
[/in_email_list]
```

***

**\[not\_in\_email\_list]**

Displays content if the user's email is **not** in a predefined list.

* **Usage**:

```
[not_in_email_list]
    Content for users not in the email list.
[/not_in_email_list]
```

***

### Parameters

The `no_access_message` parameter specifies the text to display when a user does not meet the criteria of these access settings shortcodes.&#x20;

**Details:**

* **Type**: Text
* **Default Value**: Blank space
* **Usage**:&#x20;
  * Set `no_access_message="You do not have access to this content"`&#x20;

***

Each shortcode can be nested within others for more granular visibility control. Make sure to test combinations for the desired effect!


---

# Agent Instructions: 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:

```
GET https://docs.wavecast.io/publishing/shortcodes/access-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
