Introduction
WPO365 Audiences will help you to restrict access to individual WordPress posts and pages either by requiring that a user is signed in or by demanding that the user is a member of an (Azure AD Groups based) Audience.
Each audience is a group of users that is dynamically populated with members of one or more Azure AD groups. When you create or edit Audiences you give them a name e.g. “All internal Employees” and you enter one or more Azure AD group IDs. Audiences is a feature that you must be enabled before they can be created, edited and deleted and before they become effective.
Supported features
Audiences for Authors
For the author to use Audiences is as simple as adding a new WPO365 Audiences Guten block to it as shown below.
An administrator may decide to instead enable the use of the Audience Gutenberg Block. If enabled, authors can simply add an Audience Gutenberg Block to a post or page instead.
If the user has no permissions to see the page, then the WPO365 plugin will:
- Show a 404 NOT FOUND error when the user has entered the URL directly in the address bar of the browser.
- Remove the page from possible search results.
- Not show the page on archive pages.
Audiences for administrators
Administrators can create, edit and delete audiences and is a simple as defining a name for the audience and adding one or more Azure AD group IDs to list. In addition, you can define roles and (custom) post types for which the plugin will not apply audiences.
Users are automatically assigned to an audience by the plugin when the feature is enabled whenever they sign in with Microsoft or users are synchronized from Azure AD.
Whenever the feature is enabled a new column Audiences is automatically added to the default WordPress Users list, helping administrators to track the current audience assignments on a per-user basis.
Plugins with this feature
The following plugins allow you to enable the Audience feature: