Access and permissions
Performance Matters has two layers of security:
Menu Security - Each user requires security permissions for the menu options they can access.
Object Permissions - Each user must be permitted to access individual objects.
There are two administrator permission levels.
Menu security
Menu security determines which menu options a user can access from the main navigation menu. Site administrators define menu security.
As a best practice, assign users to groups with menu security inherited from group settings. The menu security is then a superset of their group assignments.
Follow these steps during your initial user setup:
Create user accounts. Give each user unique login credentials and have them sign in to confirm.
Create groups based on roles. Plan these carefully because they are the basis for menu security for all system users. Refer to Administer Groups for instructions on creating groups.
Assign group menu security. Refer to Set Menu Security for instructions on setting menu security.
Create review boards. Refer to Administer Review Boards for instructions on creating review boards.
Assign administrator permissions to the appropriate groups. Refer to Administer Organizations for instructions on assigning admin and high stakes admin permissions.
As a best practice, create a group of reviewers to establish permissions and menu securities for the group. Then, choose the reviewer group as a member of the review board.
Object permissions
Permissions determine which objects a user can access and whether the user can review, update, or administer those objects. Grant group or user permissions to an object based on their role.
Review the instructions for each object type for specific definitions and settings recommendations and requirements.
If you give a user update or administration permissions to an object, they can edit it without notifying the original creator. This includes making changes to its name, configuration, content, and other properties.
Add permissions
Click the global search icon to locate the object.
Select the object Type.
Enter Search criteria, then press Enter.
Click the object's Edit icon.
Make the necessary changes to the permissions.
Click Permissions.
Click Add group.
Choose users and groups.
Search for the user or group using the Group Type, Organization, Description, or User's Groups (role).
Click the user or group row.
Press and hold the Ctrl or Cmd key to make multiple selections.
Click OK.
Select the permissions in the header to apply or remove the permissions for all users and groups. You can add or remove permissions from individual users or groups as needed.
Click Save.
Permission levels
The following permissions determine what you can display and the available actions:
Read provides access to display objects.
Copy allows objects to be displayed and copied.
Update allows objects to be copied and updated.
Admin provides access to manage permissions. Users who have administrative permissions have access to all site objects.
Access allows users to display reporting data.
Report provides access to all reports associated with the object.
High_stakes_admin gives access to any objects with the high stakes attribute.
File_uploader provides the ability to upload files.
Administrator permissions
There are two levels of administrator permissions. A Site Administrator must assign both during organization administration.
Click your initials, then choose Manage Organization.
Click Site Permissions.
Admin (Site Administrator)
Users with a Site Administrator role can administer any objects within the organization and perform administrative tasks for the organization.
All administrative users have Admin level permissions to all objects within the organization by default. These permissions supersede all other menu or object securities.
Administrative users also have High Stakes Admin permission by default.
High Stakes Admin
High Stakes Admin is the highest level of security for the site. Site Administrators can make changes to anything within their district’s site.
Only users with High Stakes Admin permission have access to high-stakes tests. After a test is designated as high-stakes, reviewing or interacting with the test or its items is restricted.
A test becomes a high-stakes test if a High Stakes Admin selects Test Security (High Stakes) on the Administration tab of the Edit Test page. Only users with High Stakes Admin permission can display or select this option.
Refer to Build a Test for more information on Test Properties settings.
For a user to access high stakes content, the following must apply:
The user must be assigned High Stakes Admin permissions.
Unless the user is a Site Administrator, they also must have permission to the high-stakes test and its items. Only Site Administrators have permission to access all objects.
Administrative users have High Stakes Admin permission by default.