Permissions to Allow Advisors to Register, Drop, and Withdraw Students
For advisors to register their advisees for courses, they need the "Can register advisees" permission. For advisors to drop courses for their advisees, they need the "Can drop courses for advisees" permission.
Both permissions are available in the following roles (and roles copied from them):
Primary Advisor - Access to Assigned Students
Secondary Advisor - Access to Students by Academic Program
Secondary Advisor - Access to Students by Athletic Roster
Secondary Advisor - Access to Students by Campus Location
The general outline for giving advisors permission to register and drop students includes the following steps:
Copy roles, and use the copies. Leave the default roles unedited and unassigned.
Select permissions.
Add users to the role.
Give the role access to the Advising module.
For secondary advisor roles: Associate the role with specific programs, sports, or locations.
We recommend using copies of roles rather than the original templates. You can make as many copies as you need to suit your specific needs, and it keeps the original templates intact. You can make more specific Secondary Advisor roles as needed, such as one for each campus or one for assistant coaches.
If you haven't already made copies of the Primary Advisor and Secondary Advisor roles to work with:
From the Advising Administration hub, click the Hub options drop-down.
Select Settings and Roles and then Advising Roles. The Academic Advising Roles page opens.
Copy a role:
On a Primary or Secondary Advisor role's row, click the Options drop-down, and select Copy. The Copy Role page opens to the Choose Template stage.
Edit the New Role Name field and the New Role Description field to suit your purposes.
Click the Save and continue button. The Copy Role page advances to the Define Access stage.
Select the checkboxes for Can register advisees and/or Can drop courses for advisees.
Consider whether to grant other permissions, too. Permissions relevant to registering include the following:
Can clear to register
Can perform registration approval
Can grant [one of the following] overrides:
Course authorization
Course full
Course prohibited
Schedule conflict
Click the Copy role button. The role is saved, and the Academic Advising Roles page reappears.
Repeat the steps to copy other roles as necessary.
Follow the steps in the If You Already Have Copied Roles section to add users and modules to the role. You can also associate secondary advisor roles with programs, sports, or locations.
If you already have copies of Primary Advisor and Secondary Advisor roles to work with:
From the Advising Administration hub, click the Hub options drop-down.
Select Settings and Roles and then Advising Roles. The Academic Advising Roles page opens.
On the row of the Primary Advisor or Secondary Advisor role you want to work with, click the Options drop-down, and select Edit. The Edit page opens to the Permissions tab.
To select the permissions:
Click the Edit button.
In the Registration Management category, select the checkboxes for Can register advisees and/or Can drop courses for advisees.
Consider whether to grant other permissions, too. Permissions relevant to registering include the following:
Can clear to register
Can perform registration approval
Can grant [one of the following] overrides:
Course authorization
Course full
Course prohibited
Schedule conflict
Click the Save button.
To add users to the role:
Click the Users tab. If the users who need this permission aren't there, click the Add to Role button. The Add to Role pop-up opens.
Begin entering the advisor's name or ID, and select from the list.
Click the Add to Role button. The advisor is added. Repeat to add other advisors.
To give the role access to communications (emails, texts, To Dos, etc.) in the Advising module, click the Module Access tab. On the rows for Advising and Advising Meeting, click the buttons so they say Yes.
Tip
Selecting the Advising module grants access to communications in Advising in general. Selecting the Advising Meeting module grants access to communications connected with Advising Meeting Notes.
For secondary advisor roles, associate the role with an academic program, a team, or location.
Click the Associations tab.
In the Student group or Athlete group drop-down, select an option (sport, location type or program type). The list for the selected option opens.
In the Access column, click the button to make it say Yes for the programs, teams, or location you want the role associated with. Advisors will have access to students in those programs, teams, or locations.
No. Permissions for adding students to a waitlist or moving them from waitlisted to currently registered are in the Registration Override and Access Control role (and roles copied from it) in the Registration module.
No. After the drop deadline, your school might allow students to withdraw themselves or might require the registrar's office to do the withdrawing. Permissions for withdrawing students are in the Registrars and Registration Module Manager roles (and roles copied from them).
Yes, if they have permission. Permission for students' holds are assigned in the Person Management role in the System Administration module.
Warning
Before giving advisors access to student holds, consider privacy issues, FERPA, and any other constraints that might affect an advisor's right to view a particular hold type.
Permissions tab: "Can view holds"
Associations tab
Related Information Group: Hold Type
For each hold type that advisors need access to, select an accessibility level:
None
View
Add
Add and remove
Admin: Users with this access can delete holds as well as view, add, and remove them. Removing means setting an end date—if effect, expiring a hold. Deleting means expunging the hold so no record of it exists.
Most of the permissions needed for student information are in the primary and secondary advisor roles. However, to view certain' contact information for students, such as email address, advisors need the "Can view alternate contacts" permission on the Person Management role in the System Administration hub.