Administrators, Authors, Custom Author roles and Reviewers


There are three different user roles in dominKnow | ONE, although your site may not have all three roles available.

Each allows different access and permissions in the system.

Permission settings depend on the role:

  • Administrators are the highest-level authoring role. An Administrator can access all content within your authoring site and has permission to edit and make changes to any Project. An Administrator can manage Author and Reviewer roles in order to assign them to Projects as well as deactivate or reactivate these users. Plus an Administrator has a number of other important permissions and responsibilities, which we've gathered together in this Collection here
  • Authors are a more limited authoring role. Authors have access to Projects they make themselves but do not have access to Projects made by other Authors or Administrators unless they've been assigned to the courses. Authors have access to company assets, assets for Projects they are assigned to, and access to any assets they themselves have uploaded. By default Authors can manage Reviewer roles in order to assign, deactivate, or reactivate these users. Custom Author roles can also be defined, giving your organization even more control over an Author's permissions.
  • Reviewers have no authoring permissions. They only have access to view and add feedback (Reviewer Notes) to projects they have been assigned to.

What roles does my dominKnow | ONE site have?


If your dominKnow | ONE subscription is Solo or Teams, then your “creators” will all be Administrator-type authors.

And that makes sense. For example, if you have a team of three authors, odds are that everyone should have access to all the content in order to maintain or update it. 



The Author role is only available for Business and Enterprise-level subscriptions. 

It’s typical for larger teams, especially ones that include different departments, to have a mix of Administrators and Authors. For example, there are likely reasons the HR authoring team shouldn’t have access to the Sales team's learning content. Setting up each department's creators as Authors means their access permissions can be controlled. 

Another good use case for Authors is when using external vendors to create content – the Author role means they can access the content they are contracted to work on, but not access any other content at all.

These subscription-levels also include the ability for Administrators to create Custom Author roles, such as Authors who can only work in Flow or Claro, or who don't have publishing privileges, and many more options. 

This resource outlines how to create and manage Custom Author roles.



All subscription levels include Reviewers. And no matter what dominKnow | ONE subscription level you have, Reviewers are free and unlimited.  

  0     0

Similar Projects

Questions  ( 0 )