Publishers

Every page can have one or more owners. Owners are responsible for maintaining the content on their pages, and are the first point of contact for any issues that arise.

Ownership cascades down the page hierarchy, so that the owner of a parent page is also the owner of all its child pages. This means that publishers are responsible for the content they own, and for the content owned by their team members.

By importing edit history from your CMS, PageQA can identify the publishers who have made the most changes to a page within the last six months. These are the people who are most likely to be familiar with the content, and are best placed to review it for accuracy and relevance. Provisionally assign ownership to these users and ask them to confirm or reject it.

Offboarding

Managing the content lifecycle across a large organisation means having a plan in place for when publishers leave the organisation (offboarding). This is particularly important for content that has no other owners, as it can become outdated and irrelevant without anyone to maintain it.

PageQA can help you identify content that is owned by deactivated users by connecting to your organisation’s user directory. We support a number of protocols for this, including LDAP, Active Directory, and SCIM.

If there are no other owners for the pages owned by a deactivated user, PageQA will notify the owner of the nearest parent page. They will be asked to review the content and either label it as archivable or assign a new owner.

Authentication

Large web estates often have an equally large number of publishers. Managing access to the content management system can be a challenge, particularly when publishers are spread across different teams and departments. PageQA supports a number of authentication methods to integrate with your organisation’s existing identity provider, including:

• OpenID Connect
• SAML
• LDAP
• Active Directory
• Email

We recommend using OpenID Connect for single sign-on (SSO) with your organisation’s identity provider. This means that users can log in to PageQA using their existing credentials without having to be provisioned separately.

For email authentication, we’ll limit access to users with email addresses from your organisation’s domain. This is a simple way to restrict access to your organisation’s users without having to integrate with a full identity provider. You can decide whether to allow users to sign up with their email address, or whether you want to provision users manually.