What are the different types of users?
This article will describe the different types of users that can be created in your ScreenSteps account.
NOTE: Only Admin and Editor users count against the maximum Author total for your account. You can have as many Reader or API Access users as you want.
Admin users are authorized users on your account. They can:
- Post and update content.
- Delete/reorganize content.
- Manage users, groups and custom templates.
- Edit site settings.
Admins can access all content in your ScreenSteps account.
Editor users are authorized users on your account. Before an Editor can do anything they must be assigned to one or more sites.
Once an Editor is assigned to a site they can:
- Create manuals in a site.
- Publish manuals in a site.
- Publish articles to manuals in a site.
- Moderate comments for the site.
Any of these privileges can be limited. Read more about the editor permissions here.
They can not manage users, groups or custom templates.
Learners can be granted access to protected sites on your account. They do not have access to the admin area and cannot alter content on your ScreenSteps account.
- They are only available on the Employee Training Plan
- Learners can be assigned to Courses and can use the ScreenSteps Browser Extension for viewing contextual help.
Reader users can be granted access to protected sites. They do not have access to the admin area and cannot alter content on your ScreenSteps account. Readers are different from Learners in the following ways:
- They do not have access to Courses
- They do not have access to the ScreenSteps Browser Extension
API Access Users
An API Access user functions the same as reader users with two significant differences:
- When a user is logged in as an API Access user they can't change their password or access their profile settings.
- API Access users have no email address associated with them.
Use API Access users whenever you are granting a group of people access to a space with a single login. Some examples might be embedding login credentials in urls or embedding a ScreenSteps iframe in a page.