Setting User Roles and Rights

Prev Next

Roles and Rights Overview

To get started, users can view the Eduphoria Roles and Rights Spreadsheet. It contains the Roles, Rights, and descriptions for all Eduphoria applications. Although this document is not printer-friendly, it provides detailed information on roles and rights, and can be downloaded and edited as needed.

Use the tabs at the bottom of the spreadsheet to view information about roles and rights for each application.  

RRoles1.png

Users with the System Administrator role can grant roles to other users. No roles are assigned by default when all users are imported for the first time.

The majority of users do not need any roles. Directors, administrators, and principals require additional access levels to be granted.

To assign user roles and rights, click on Users ( person_outline ) and use the search box to locate a specific user. Click on an individual user to view their profile and access the Roles tab to grant additional access.

User management interface displaying roles and permissions for a specific user.

Built-in Roles Per Application

System administrators can assign users built-in roles or custom roles. Each Eduphoria application, with the exception of Facilities&Events, has its own set of built-in roles within Management. Districts that use Secure File Transfer Protocol (SFTP) to import built-in roles can review the following application names and role names to help ensure a successful import.

Note: Roles that have a plus sign ( add ) next to them are location-specific. You can grant the user role access at all schools or grant them access at some schools, and then select the specific schools.

Aware Roles

The built-in roles for Aware are as follows:

  • Data Administrator

  • Principal

  • District Data Viewer

  • Student Inventory Administrator

  • Student Forms Administrator

  • Campus Forms Administrator

  • Campus Administrator

  • Campus Local Assessment Printer

  • Item Bank Administrator

List of Aware's administrative roles with checkboxes for selection.

Forethought Roles

The built-in roles for Forethought are as follows:

  • Curriculum Manager

  • Principal

  • Lesson Plan Viewer

  • Denied Access

A list of Forethought roles with checkbox selections.

Formspace Roles

The built-in roles for Formspace are as follows:

  • Formspace Administrator

  • School Administrator

  • Public Web Administrator

  • Deny access to SchoolObjects:formspace

Options for different administrator roles for Formspace.

Helpdesk Roles

The built-in roles for Helpdesk are as follows:

  • Denied Access

  • Principal

  • Superintendent

A list of Helpdesk roles with checkbox selections.

Strive Evaluation Roles

The built-in roles for Strive Evaluation are as follows:

  • Appraisal Administrator

  • District Appraiser

  • School/Department Appraiser

  • School/Department Limited Appraiser

  • Appraisal Viewer

  • District Walkthrough Appraiser

  • School Walkthrough Appraiser

  • Walkthrough Viewer

A list of Strive Evaluation roles with checkboxes for selection.

Strive Professional Learning Roles

The built-in roles for Strive Professional Learning are as follows:

  • Professional Development Administrator

  • District Course Editor

  • School Course Editor

  • Limited Course Creator

  • Professional Development Credit Approver

  • Professional Development Credit Viewer

A list of Strive Professional Learning roles with checkboxes for selection.

Management Roles

The built-in roles for Management are as follows:

  • System Administrator

  • Roster Administrator

A list of Management roles with checkboxes for selection.

Best Practices for Roles and Rights

Only a few users should be system administrators. One system administrator may not be enough, but 30 is too many. Users with system administrator access have the greatest level of access within Eduphoria and can grant any and all rights to themselves.

Each Role has certain Rights associated with it. When a role is assigned to a user, a collection of rights is automatically granted to the user.

Caution: Some rights are not inherited by a specific role and must be assigned manually. One example is the right to impersonate other users.

Do not randomly assign rights. Assign roles and only edit rights as needed since editing rights can remove access if not carefully applied.

Checking all roles does not give a user more rights. In most cases, the first role listed in each application grants the user administrator access for that application

You can run separate reports of the users assigned roles and one of the users assigned specific rights.

Tip: You can determine whether new users are granted Built In Roles or a Custom Role using the Default new users to setting on the Security tab of District Settings. For more information, see Enabling Custom Roles.