Understanding user roles and access levels

In Elucidat Create, there are two ways to manage what users can see and do: by assigning a user role and setting access levels for content.

This article explains how they work, their scope, and what exceptions apply.

Contents

1 Overview

2 User roles

i Quick reference guide

3 Access levels

i Quick reference guide

4 Important information about Administrators

Summary: User roles vs access levels

User roles are profiles that can be assigned to the users in your account. They give a user a pre-determined set of permissions enabling them to carry out certain actions in the account. A user's role can only be assigned or changed by an Administrator.

Access levels are used to configure whether Projects, Brands, and assets you've created are visible to other users. A user's access level on a piece of content is set by the content's Owner—the original creator of the content.

You might think of a user role as a person’s job title, and access levels as the keys they have to different filing cabinets. A person's job title and responsibilities stay the same, but their ability to carry out those responsibilities can be enabled or limited by the filing cabinets they can access.

For example, a user with the Author role can edit Projects but only for those they have access to as an Editor or Owner. 

Read on for a detailed breakdown of each user role and access level.

User roles

There are three possible user roles in Elucidat Create that you can assign to your users.

• Administrator—has full access to all aspects of the account including user management and viewing Analytics
• Author—may create Projects and Brands, upload assets,
• Restricted Author—has the same permissions as an Author except those relating to exporting content from the platform.

Quick reference guide

Here is a quick reference guide to the key permissions that each role grants.

Access levels

There are three access levels:

• Owner—assigned to the creator of the content. As the Owner, you are permitted to carry out all management actions for the content, including deletion.
• Editor—can view and edit the content but they are not permitted to delete it
• No access—cannot see or access the content

Users are automatically assigned as the owner of a piece of content if they have created it.

For example, a user who creates a Project will become its Owner. They can choose to share it by updating others’ access levels to Editor.

Users who have the access level No access for a piece of content won't be able to see it in their library and therefore cannot take any action on it. However, if their access level is then changed to Editor, they will be able to see the Project and carry out any permitted actions defined by their user role.

Quick reference guide

Important information about Administrators

There are a few exceptions that apply to an Administrator.

• Administrators are able to view and edit all Projects in their organization's account regardless of their access level
• Administrators can also view all Brands and assets in their organization's account and are permitted to delete them if they are not the Owner.

Unless they are the Owner of a Project, Administrators are prohibited from:

• • Changing its access levels
  • Exporting it as a SCORM package
  • Deleting it