A key access level in your portal is that of an Administrator (Admin). An Admin is a special type of user with certain permissions to manage other users, manage training, run reports and manage your portal settings.

Admins can only be created manually. You cannot create Admins via the Upload People function. Admins access can be granted on the New Person page or when editing an existing person as part of our standard fields.

Admins can only be created and edited by a Super Admin - the highest access level of Admins. Other Admins cannot create or edit the Admin permission or Access level.

Here are the different types of Admin Access levels you can assign. We then discuss each type in detail in the sections below.

  • Super Admins. Admins with unlimited access and permissions.

  • Standard Admins. Normal admins who can manage all aspects of user people, knowledge and analytics, but cannot change some high-level Account settings.

  • Knowledge Admins. Limited admins who can manage knowledge (including settings, reporting and enrolments) but can only view people. They cannot create or edit people (other than enrolments) or change any Account settings at all.

  • Reporting Admins. Very Limited admins who can only access the Analytics area. They cannot manage knowledge, people or Account settings at all.

Super Admins

Super Admins are your most powerful Admins.

  • Super Admins have unrestricted access and permissions.

  • Super Admins can create and edit other Admins.

  • Super Admins can access all Account menus and settings.

  • Super Admins can view, create and edit users.

  • Super Admins can view, create and edit knowledge.

  • Super Admins can view and use Analytics reports.

You should have a very limited number of Super Admins as they have significant power in your portal. However, in a small organisation, it is possible that all your admins are Super Admins (out of simple necessity).

Standard Admins

Standard Admins are your 'everyday' Admins.

  • Standard Admins have some restricted access and permissions.

  • Standard Admins cannot create or edit other Admins.

  • Standard Admins can access some Account menus and settings.

  • Standard Admins can view, create and edit users.

  • Standard Admins can view, create and edit knowledge.

  • Standard Admins can view and use Analytics reports.

Standard Admins are your main type of Admin. They can help manage people and knowledge, run reports and manage some Account settings.

Knowledge Admins

Knowledge Admins are admins who generally manage training.

  • Knowledge Admins have restricted access and permissions.

  • Knowledge Admins cannot create or edit other Admins.

  • Knowledge Admins cannot access any Account menus and settings.

  • Knowledge Admins can view people, but cannot create or edit people.

  • Knowledge Admins can view, create and edit knowledge (including enrolments).

  • Knowledge Admins can view and use Analytics reports.

Knowledge Admins are useful for Admins who manage training and enrolments, but do not need to create or edit users. Knowledge Admins can still view users, to help manage enrolments and reporting. You may allow some training coordinators or key training creators access to this level.

Reporting Admins

Reporting Admins essentially have no admin permissions other than to view the Analytics reports.

  • Reporting Admins have almost no access and permissions.

  • Reporting Admins cannot create or edit other Admins.

  • Reporting Admins cannot access any Account menus and settings.

  • Reporting Admins cannot view, create or edit people.

  • Reporting Admins cannot view, create or edit knowledge.

  • Reporting Admins can view and use Analytics reports.

Reporting Admins are useful for training coordinators who only need to run reports to help plan training, some managers who want access to reporting beyond what is available on the Team page or anyone else who needs specific reporting access but not administrator permissions. Finally, Reporting Admins cannot access the in-platform Admin Chat - they will need to be supported internally by your other Admin types.

Did this answer your question?