# Targeting Content to Users

Content in Bero can be targeted to users by 2 mechanisms: Tags and Permissions.

**Tags** allow users to target their own content.&#x20;

**Permissions** allow administrators to target content at users based on group membership and login.

The additional **Sites** mechanism is a possible future capability, adding more capabilities at a reasonably low engineering cost. It would allow the targeting of not just content but interface to all users regardless of login.

## Tags

As of now most content (Courses, Lessons etc) can be assigned tags by content creators. Tags can be created in the CMS easily on the page being tagged.

![](https://1108223324-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fhandbook%2F-MfgwOWyUSjpcxOnpATh%2F-Mfgx-1CwryZyjG62fcP%2F0.png?generation=1627473052261554\&alt=media)

Tags show up in the user interface behind the filter icon, allowing users to filter the list to content matching tags

![](https://1108223324-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fhandbook%2F-MfgwOWyUSjpcxOnpATh%2F-Mfgx-1Dyx84Qyjf7IuW%2F1.png?generation=1627473052330106\&alt=media)

Tags allow users to search for the content they are interested in without hiding any content from anyone

## Permissions

Pages in wagtail can be given 3 types of permission, public, private ( logged in ), and private ( group members)

![](https://1108223324-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fhandbook%2F-MfgwOWyUSjpcxOnpATh%2F-Mfgx-1EQFA0NdaxDSEk%2F2.png?generation=1627473052321797\&alt=media)

* Public content is shown to all users
* Private ( logged-in ) content is shown to only authenticated users
* Private ( group membership ) content is shown to only members of the specified groups

Child pages obey the permission setting of their parent so a whole category / topic can be made private and its contents will be private too.

Permissions allow site admins to target content to users based on if they have a log in, and the groups they are a member of, but you must be logged in to be a member of a group.

## Sites

{% hint style="info" %}
**NOTE: This is not currently implemented**
{% endhint %}

Wagtail allows us to create multiple sites under one installation differentiated by the domain used to access the site.

We could use the same deployment to host multiple user sites, different content would be seen depending on the domain used to access the site.

![](https://1108223324-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fhandbook%2F-MfgwOWyUSjpcxOnpATh%2F-Mfgx-1FLUB0ghyDbRNH%2F3.png?generation=1627473052268428\&alt=media)

**What this would allow**

Different site domains would be able to:

* have different theming / images
* have different login help contacts
* have different languages exposed
* have different content

All content would be managed in one CMS allowing:

* content to be easily copied from one domain to another
* Single login for program staff across multiple domains
