> For the complete documentation index, see [llms.txt](https://old-manual.converia.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://old-manual.converia.de/en/general/your-own-converia-website/page-structure/create-and-edit-pages/page-content-and-modules/restrict-the-visibility-of-page-content.md).

# Restrict the visibility of page content

CMS -> Navigation -> Page structure

In some cases, it may be necessary to restrict the visibility of certain website content. In Converia, there are various ways to control access to information.

{% hint style="danger" %}
CAUTION: These measures may not be sufficient to securely protect confidential information. Users can bypass module visibility by assuming the required user role, and hidden pages could appear in search engines. It is therefore important to check beforehand whether the selected access restrictions are sufficient.
{% endhint %}

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FVHmSV6Gc0Vq1gViINQRR%2Fimage.png?alt=media&amp;token=76a06392-ab08-442f-96c1-201c48271e03" alt="Fig. 1: Restrict module visibility in page content"><figcaption><p>Fig. 1: Restrict module visibility in page content</p></figcaption></figure>

## 1. Restrict module visibility

For each article in the page structure, you can specify the user roles for which it should be visible. The visibility can be controlled for individual modules and configured in the *Content* tab of the respective page.

### Visibility selection options

* User is not logged in
* User is logged in
* User is attendee
* User is submitter
* User is author

The options can be combined, which increases the number of people authorized to access the content. For example, if the checkboxes *User is attendee* and *User is submitter* are activated, people can either be attendees **or** submitters in order to access the content. It is not necessary to fulfill both roles at the same time in order to view the content.

{% hint style="warning" %}
Only people who are logged in can be identified as attendees, submitters or authors.
{% endhint %}

If content on a page is only visible to a specific user group, it is advisable to link another article in the page that is visible to all other users and in which, for example, it is pointed out which conditions must be met in order to be able to access the content.

<div><figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FTH9PJ3lRJsybtJ6rmh2U%2Fimage.png?alt=media&amp;token=a932946b-bb88-40e6-8931-e3997b317685" alt="Fig. 2: Hint - contents only visible with login"><figcaption><p>Fig. 2: Hint - contents only visible with login</p></figcaption></figure> <figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FdgGcigXxaGpALx2xfqPH%2F2025-01-09_11h35_00.png?alt=media&amp;token=a8ab3a45-8273-4e87-b5a5-4ba0fc4c94d8" alt="Fig. 3: Hint - content only visible with login"><figcaption><p>Fig. 3: Hint - content only visible with login</p></figcaption></figure></div>

Figure 2 shows a page on which content is only visible to logged-in users. The modules with the page content are set to *User is logged in*, the notice module is set to *User is not logged in*. After logging in, users see the content and the hint disappears.

Figure 3 shows a page on which content is only visible to logged-in users. The modules with the content are set to *Person is attendee*, the hint module is set to *User not logged in* and *User is logged in*. The hint appears for everyone who is not logged in and disappears after logging in if there is a valid login.

## 2. Create a hidden page

Another way to make content accessible only to a specific group of people is to create a page that cannot be accessed anywhere in the menu or via links within articles. This means that only those who have the direct link to the page can access it.

#### Procedure

1. Create [articles](/en/general/your-own-converia-website/article.md) with the desired content
2. Create a [page](/en/ticketing-processing-with-converia/page.md) in any folder of the page structure and link articles as [content](/en/general/your-own-converia-website/page-structure/create-and-edit-pages/page-content-and-modules.md)
3. Open the preview (Fig. 4).
4. Copy the link from the URL line of the preview
5. Send the link to authorized persons via e-mail

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FT7D2uD5IOFjtZ8lQZxpy%2Fimage.png?alt=media&amp;token=ca7a674e-54c7-47b6-b888-bbe5da595caf" alt="Fig. 4: Open the preview"><figcaption><p>Fig. 4: Open the preview</p></figcaption></figure>