User Administration Guide

When you are adding users to your Agility CMS instance it's important to think about what Role that user will have in managing your instance and your content.

Choosing the right permissions (roles) when adding users gives them a safe and streamlined environment when viewing or editing content. When adding users, you should select the bare minimum role that users will require.

This guide we'll go over some of the best practices when adding new users and permissions in your Agility CMS.

What We'll Cover

  1. Adding a user who can only view Content without Editing/Publishing
  2. Adding a user who should only be able to Edit/Publish Content
  3. Adding a user who can only manage specific Pages/Content.

Adding a user who can only view Content without Editing or Publishing

Adding a user with the Reader role permission will grant them access into your Agility CMS, but only allow then to view your content without being able to Edit or Publish new content or modify any of your Content Models.

<i>The figure above shows a user with the <b>Reader</b> role permission. Buttons like Add New or Delete are revoked from this user and text fields are greyed out (uneditable).</i>

Adding a user who should only be able to Edit or Publish Content

Adding a user with the Editor role grants them access to edit and create new items on the site. This user, however, can only save content and not approve or publish items.

<i>The figure above shows a user with the <b>Editor</b> role permission creating a new blog post.</i>

Adding a user with the Publisher role grants them access to publish content or pages, in addition to edit access.

<i>The figure above shows a user with the <b>Publisher</b> role permission creating a new blog post with the ability to publish.</i>

Adding a user who can only manage&nbsp;specific&nbsp;Pages or Content

Sometimes you may want a user to be able to modify some specific content. This can be done by setting a user's role to Reader and setting security roles on the specific page or content item you want them to modify. Let take a look at an example of this.

After setting a user's permission to Reader, I want to go ahead and grant him the ability to only manage content within the Home Page.

On my Home page, I can navigate to the Security tab and add a new user to the list. This is a list of the users who have specific access to this item.

After selecting a user, I can then select the role I want to give them from the list and submit. In my case, I'll give this user Publisher permissions.

When the user is logged into Agility CMS with their new User Permission roles, the specific content (in this case the Home page) will be editable, but the other pages or content will not be.

Home Page (editable):

Contact Page (non-editable):