Anchor | ||||
---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This section demonstrates how to add users, change passwords, assign and create roles, and set permissions within the system. |
Anchor | ||||
---|---|---|---|---|
|
In the User section you can attach users, change passwords, indicate the type of user, and inactivate a user when necessary.
From the Administration and Maintenance tab, select Users.
Attach User(s)
Click the Attach User(s) button in the ribbon.
Info The list of users is established in the Admin Console. A new user must first be added into Admin Console before it is available to attach in the MSA Client.
- Select the User from the list or use the search function to locate a particular user. Then, click Ok.
School to the bottom of the User Maintenance window to locate the new user and establish User Information. Then, click Save Changes.
- Full Name - Enter the user's full name.
- Email Address - Enter the user's email address.
- Inactive - If a user no longer requires access to the system, place a checkmark in the inactive box.
Roles - Place a checkmark in the box to define the user's role.
Info Permissions allows you to set restrictions for each user role.
- System Administrator
- Normal User
- User-Defined Role(s)
Change Password
- Select the user from the list and click Change Password.
Enter the New Password and then Confirm Password. Then, click Ok.
Info As an Administrator, you have the ability to reset user passwords without entering the old passwords. Non-administrators will need to enter the old password before changing.
Info Passwords must contain at least one (1) letter and one(1) digit or punctuation and must be at least six (6) characters. e.g. apply1
Anchor | ||||
---|---|---|---|---|
|
Roles match the users with Security and Permissions within the system.
- From the Administration and Maintenance tab, select Roles.
- Create a new role. Then, click Save Changes.
- Description - Enter a description of the new role in the blank space with the asterisk * (typically the last row).
Template - The template is used to initially copy existing permissions when the new role is created. It is also used when permissions are added by future program updates to determine appropriate defaults.
(none) - No future permissions will ever be automatically granted to this role.
- System Administrator - All future permissions will be automatically granted to this role by default.
- Normal (recommended) - Future permissions that default to admin-only will not be granted to this role; but future permissions that default to all users will be granted by default.
AnchorPermissions Permissions
Permissions
Permissions | |
Permissions |
Defines the access and actions available within the system for a specific role.
- From the Administration and Maintenance tab, select Permissions.
Establish security levels for each permission and role. Then, click Save Changes.
Info title Permissions Information about each permission is given at the bottom of the window to further explain each in better detail.
- Select a permission from the list.
Use the drop-down menu to establish the permission setting for each Role.
None Users assigned to only one role will not have the ability to perform this function (see below for more details) Allow Users will have the ability to perform this function. Deny Users will not have the ability to perform the function. Note title Deny If a user role has been set to Deny a function and a user attempts to perform the denied task, the option of performing an override is available MAY be available depending on the nature of the operation. If the user requests an override attempt, an administrator or additional higher level role has the ability to accept or reject the override attempt. For more information on releasing override attempts, refer to Release Override Requests in the Utilities section.
Permission Matrix
Info |
---|
If a user is only assigned to one role, the None setting acts the same as the Deny setting. If a second role is assigned to the user and places an Allow setting for a function already set as None, the user will be allowed access. None will always be treated as Deny unless overwritten by an Allow. This allows secondary roles to be created that explicitly Allow or Deny a single function without having to reset every other function. |
Function | Role 1 | Role 2 | Results |
---|---|---|---|
Student Lookup | Allow | None | Allow |
Scan Form Maintenance | Deny | None | Deny |
Edit Student | None | Deny | Deny |
Process-All Applications in Review | Allow | Deny | Deny |
Import Student Data | None | None | Deny |
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|