When you are&nbsp;<a href="https://help.agilitycms.com/hc/en-us/articles/360014620951">adding users</a>&nbsp;to your Agility CMS instance it's important to think about what&nbsp;<a href="https://help.agilitycms.com/hc/en-us/articles/360026904071">Role</a>&nbsp;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.

Adding a user who should only be able to 

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.

The figure above shows a user with the Reader role permission. Buttons like Add New or Delete are revoked from this user and text fields are greyed out (uneditable). Select an Image

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.

The figure above shows a user with the Editor role permission creating a new blog post. Select an Image

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

The figure above shows a user with the Publisher role permission creating a new blog post with the ability to publish. Select an Image

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&nbsp;specific&nbsp;content. This can be done by setting a user's role to&nbsp;Reader&nbsp;and setting security roles on the specific page or content item you want them to modify.&nbsp;Let take a look at an example of this.

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

On my&nbsp;Home&nbsp;page, I can navigate to the&nbsp;Security&nbsp;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.

Overview

What is Item and Page Security and Why is it Important?

You may find yourself in a situation where you want a user who can manage or modify specific content lists or pages, but you don’t want to give them full Editor or Publisher permissions for the entire instance. This can be done!&nbsp;

1. Assign the user the Reader Role to get started&nbsp;

2. Navigate to the Content List or Page you want to give them access to, for this example we’ll use the Home Page

3. From the Home Page, click the Menu Indicator to the right, then click Security&nbsp;

5. Select the User(s) you want to manage and click Next

6. Assign them the additional Roles you want them to have for this specific Page or Content List and click Save

Note

<a href="https://agilitycms.com/docs/owners-admins/user-access">User Access</a>

<a href="https://agilitycms.com/docs/owners-admins/custom-roles">Custom Roles</a>

Best practices for controlling what user can do and which content they have access to.

Item Level Permissions

What is Item and Page Security and Why is it Important?

How to Manage Security

Note