Browse Articles
Select a Product
null Support Directory
Browse all null articles. (Last Updated
No articles found.
Search Results
No articles found.
Articulate 360 Teams: Permissions and Tasks
Article Last Updated Feb 19, 2026
This article applies to:
In Articulate 360 Teams, permissions determine what your team members can access and do, so assigning permissions is a key part of managing a team. In this article, you'll learn about the different permissions available and the tasks they enable. You’ll also find out how to transfer team ownership to someone else and why we recommend adding multiple admins to your team.
- Understanding Permissions
- Understanding Tasks for Each Permission
- Transferring Account Ownership
- Designating a New Admin When None Are Available
Understanding Permissions
Permissions control three primary functions:
- Creating: content creation and authoring
- Managing: team, group, account, and billing management
- Distributing: learner, settings, and group distribution in Reach 360
The tables below outline each type of permission within those functions, clarifying what each permission grants access to and how that impacts the number of licenses on the team.
Creating
|
Permission |
Description |
|
Creator |
A member with creator permissions can use Articulate 360 apps, including Storyline 360 and Rise 360, to create e-learning courses and collaborate on projects. They can also submit content for publishing to Reach 360, if it has been activated. Assigning a team member creator permissions uses up a creator license. A member can only have creator permissions from one team at a time. |
|
Localization |
If a team is subscribed to Articulate Localization, members with creator permissions can also be granted localization permissions. Localization permissions allow a team member to initiate translations in Rise 360 and Storyline 360. |
Managing
|
Permission |
Description |
|
Account Owner |
The person who bought the subscription is automatically assigned account owner permissions. Account owners can access billing management, and they are the only team members who can buy additional creator licenses. Except for subscriptions purchased through global resellers and distributors, this member is also assigned primary admin permissions. The account owner is not always assigned creator permissions and 360 admin permissions.
Members can have account owner permissions on multiple teams but can only have creator permissions from one team at a time. |
|
Primary Admin |
The primary admin permission is automatically assigned at the start of the subscription and can’t be removed. Think of the primary admin as a “super” 360 admin, with all the permissions of a 360 admin (detailed in the 360 Admin section below) as well as some additional permissions. For example, if your team has activated Reach 360, the member with primary admin permissions also has owner and Reach admin permissions there. They can also enable SSO for learners, change the team's subdomain, and change the team’s URL to a custom domain. |
|
360 Admin |
Members with 360 admin permissions can manage all members and groups for the whole team. They can't make purchasing decisions, but they can request that the account owner buy more creator licenses as the team grows. They can also activate or deactivate Reach 360. Members with 360 admin permissions don't consume creator licenses by default, so you can assign the permission as often as necessary. However, if the member with 360 admin permissions also wants to create e-learning courses, they should be assigned a creator license so they can use the Articulate 360 apps. If the team has activated Reach 360, members with 360 admin permissions can also grant Reach 360 admin, manager, and reporter permissions. If they also need to manage Reach 360, they must have at least one of these permissions. Members can have 360 admin permissions in multiple teams but can only have creator permissions from one team at a time. |
|
Group Manager |
Members with group manager permissions can manage members in groups for which they are responsible. They can’t manage other groups, and they can’t assign permissions related to Reach 360 and distribution. Those with group manager permissions can't make purchasing decisions, but they can request that the account owner buy more creator licenses as the team grows. Members assigned group manager permissions don't use up licenses (by default), so you can assign that permission as often as needed. However, if that member also wants to create e-learning courses, they should be assigned a creator license so they can use the Articulate 360 apps. Members can have group manager permissions in multiple teams but can only have creator permissions from one team at a time. |
Distributing
|
Permission |
Description |
|
Reach Admin |
Members with Reach admin permissions can manage all learners, training settings, and more in Reach 360. Assigning this permission does not use up a license. |
|
Reach Manager |
Members with Reach manager permissions can only manage groups to which they're assigned. Assigning this permission does not use up a license. |
|
Reach Reporter |
Members with Reach reporter permissions can access the reporting dashboard. Assigning this permission does not use up a license. |
Check out Reach 360: Understanding User Permissions and Tasks.
Understanding Tasks for Each Permission
The tables below detail the tasks that can be performed in an Articulate 360 Teams account, along with the permissions that a team member needs to be assigned to be able to do them. To learn more about these tasks, see the Articulate 360 Teams user guide.
Creating
|
Task |
Account Owner |
Primary Admin |
360 Admin |
Group Manager |
Creator |
|
Use the Articulate 360 apps to create e-learning courses and collaborate on projects |
|
|
|
| |
|
Translate content with Articulate Localization |
|
|
|
|
Managing the Subscription
|
Task |
Account Owner |
Primary Admin |
360 Admin |
Group Manager |
Creator |
|
Own a team or teams |
| ||||
|
Make purchasing decisions, such as buying additional licenses for the team |
| ||||
|
Name or rename the team |
|
|
|
| |
|
|
| ||||
|
|
| ||||
|
Access Reach 360 owner permissions |
| ||||
|
Manage multiple teams or subscriptions |
|
|
|
| |
|
Switch between teams or subscriptions |
|
|
|
|
|
Managing Groups and Users
|
Task |
Account Owner |
Primary Admin |
360 Admin |
Group Manager |
Creator |
|
Add and remove team members |
|
|
|
| |
|
Assign creator permissions, including for Localization |
|
|
| ||
|
Bulk-import users via CSV file |
|
|
|
| |
|
Assign “manage” permissions |
|
| |||
|
Assign “distribute” permissions |
|
| |||
|
Add, rename, and delete creator groups |
|
|
|
| |
|
Assign licenses to creator groups |
|
|
|
| |
|
Remove creators from all groups (move to Ungrouped) |
|
|
|
| |
|
Move creators to groups |
|
|
|
|
Distributing
Read this article to understand Reach 360 permissions and tasks.
Transferring Account Ownership
Articulate 360 Teams subscriptions can have multiple team members assigned 360 admin permissions, but each subscription can have only one member assigned account owner permissions and one assigned primary admin permissions. (The same member can be assigned both permissions.) The team member with account owner permissions is the only person who has access to billing management.
Account owner and primary admin permissions can’t be removed or transferred to someone else from the account management console, but we can help with that. Contact us with authorization from the current account owner or primary admin and the following details for the new account owner, and we'll take care of it for you.
- Name
- Email address
- Phone number
Designating a New Admin When None Are Available
Only members with primary admin and 360 admin permissions can add more admins to your team. Since admins don't consume licenses by default, you can assign as many admins as you like. We recommend assigning more 360 admins than you think you might need, even if they don't regularly manage Articulate 360. They can be backup admins in situations when no one else is available. This is important because we can’t change a team’s user permissions—only a member with admin permissions can.