Roles and Permissions Guide

ClassRanked Federated Roles & Permissions Documentation

Note: This document describes current functionality as of April 2026. Please check back for updates.

Not sure how to assign roles and permissions to your administrators?

Below, we break down the existing roles in ClassRanked by their abilities to help you get your team the appropriate access. By utilizing a federated permissions model, ClassRanked allows you to delegate administrative tasks while ensuring data privacy is maintained.

Use this guide to match a user's real-world responsibilities—such as managing surveys for a specific department or viewing institution-wide reports—with the correct system role and "Academic Unit" scope.

Role Types

1. Account Owner (Highest-level Role)

• Intended for: Your institution’s primary Point of Contact with ClassRanked.

  Key Capabilities: Full visibility and edit rights across all academic units; can create other Account Owners and System Managers.

  • Example: A Provost or Lead Administrator who needs to oversee every College, School, and Department across the entire University.

2. System Manager

• Intended for: Admin staff who configure institution-level information but do not need to view reports.

  Key Capabilities: Can edit institution-level settings; must assign themselves a scoped role (Owner/Viewer) to see specific reports.

  • Example: An IT Specialist who manages system integrations and user permissions but is not involved in reviewing faculty performance data.

3. Owner (Scoped Owner — “Mini Account Owner”)

• Intended for: College, school, or department leaders who need broad oversight within their specific scope.

  Key Capabilities: Can manage data, assign roles to others, and view reports for their assigned Academic Unit only.

  • Example: The Dean of the College of Arts & Sciences, who can manage all departments under them but cannot see data for the College of Engineering.

4. Editor (Scoped Editor — “Mini System Manager”)

• Intended for: Department-level admins who help Owners set up surveys.

  Key Capabilities: Can manage configurations and assign roles within their scope, but cannot view reports.

  • Example: An Administrative Assistant in the History Department who handles the logistics of survey setup but does not have permission to view the final results.

5. Viewer

• Intended for: Users who need read-only access to data and reports.

  Key Capabilities: Read-only access restricted strictly to their assigned scope; cannot edit any settings or roles.

  • Example: A Department Chair who only needs to review reporting data for their specific faculty without making changes to the system setup.

User Management (Scope Enforcement)

• Rule: Owners and Editors can only manage or assign roles to people within their assigned Academic Unit.
  • Example: A Biology Department Owner can promote a student worker to a Viewer for Biology, but they will not even see the option to add that student to the Chemistry Department.