General

Your content in Yonder is dynamic and not a static document. You can create user-specific profiles to make sure your staff always get the right information at the right time.

Dynamic content allows to only display content that is relevant for a specific role and/or a specific task. To that end, tags are attached to each information module, allowing for dynamic content filtering to take place. You can define as many roles and filters as they need and change these whenever necessary. Roles and filters are selected in Yonder using the filter tab in the menu bar. Roles and/or filters can also be assigned in the AD directory and can be pre-defined for each user. Roles and filters also work in combination with the search functionality.

In the example below, an airline operates under an AOC in Switzerland and an AOC in Germany. Users see different content depending on what AOC they operate under. Chapter numbering can be chosen freely, and the different content can also be shown under the same chapter number.

Filter and Roles

Roles and filters limit the visible content within a document to what's relevant to a user's particular role and / or mission. Roles and filters also work for entire documents (see role settings for details on that).

Filters

Filters (may be called differently in your setup) limit the visible content of a document in a way that only the following information modules are displayed:

• Information modules that are explicitly tagged with the corresponding filter criteria. No more, no less.
• Outline (TOC) limited to those items that explicitly match filter criteria.

The animation below shows a generic example of how the selection of a document-specific “By Heart Items” filter limits the visible content to information explicitly tagged with the aforementioned filter.

Roles

Roles limit the visible content of a document such that only the following information modules are displayed:

• Information modules that are tagged with the corresponding role(s)
• Information modules that are not tagged with any role tag, i.e. modules that are relevant to everyone, regardless of their particular role within the organization.
• Outline (TOC) is limited based on the same logic.

The animation below shows a generic example of how the selection of a document-specific role named “Switzerland” limits the visible content according to the aforementioned specifications.