The Basic Settings page offers institutions to manage settings related to student experience and transaction logic.
Users with the Admin role can manage appeal transactions under Settings > Basic.
Manage Basic Settings
The Basic Settings page is broken up into multiple broad sections containing settings related to each other.
Account Creation and Management
This section allows the institution to manage visibility of profile settings and how the office of financial aid will be referenced to the student.
- Enable Student Profile Management: Allows institutions to manage whether or not the student will have access to their CampusLogic profile page. If enabled, a "Profile" menu item will appear in the top right profile dropdown menu along with "Logout". If disabled, "Profile" will be hidden from students.
- Please Note: It is highly encouraged to keep this enabled, as it will allow the student to access their communication settings - managing their contact email and phone number, as well as being able to opt in/out to email and SMS communications.
- Institution Office of Financial Aid: Allows institutions to define the title of the financial aid office and how it should appear on the student side. There are many tags used on the student side that will bring this value in. By default the label will be defined as "Office of Financial Aid", which is what students will see.
A transaction is the set of tasks required to complete a file (e.g. Verification, Dependency Override, SAP Appeal). When a student is completing tasks in student self-service, there is a final step to "Finish" the file. This locks the documents and adds the student's file to the file review workflow. In the Transaction section of Basic Settings a school can choose to automatically click the Finish button for files on the student's behalf after a predefined period of time.
- Enable Transaction Auto Complete: Allows an institution to manage whether or not the system will automatically auto-submit the entire transaction if all tasks within have been completed and submitted
- Hours Until Transaction Auto Completes: When "Enable Transaction Auto Complete" is enabled, this setting controls how many hours after the last task to be submitted to auto-submit the transaction
- Please note the following:
- It is highly recommended to set it to at least one hour in order to allow students to make any necessary edits, if needed
- Entering '0' hours will cause the file to be completed when the last task is completed
- This setting only clicks the final Finish button after the student has submitted all of their tasks. This setting does not click the submit button on individual tasks.
- Please note the following:
- Enable Task Auto Submit: Allows an institution to manage whether or not the system will automatically auto-submit a task if all parts of the task are complete (web form completed, document uploaded, etc.). If enabled, each night the system will look for all tasks that are completed but not yet submitted and auto-submit them all at once.
Please Note: If both "Enable Transaction Auto Complete" and "Enable Task Auto Submit" are enabled that each night any tasks completed but not yet submitted will be auto-submitted. If all tasks are now submitted from the nightly process, then the transaction will auto-submit afterwards based on the timed setting "Hours Until Transaction Auto Completes".
- Enable Subsequent ISIR Queue: When enabled, when a subsequent ISIR is received with unexpected changes go into a separate workflow. When not enabled, subsequent ISIRs with unexpected changes continue to re-open in the file review workflow. This is for transactions in a Verified status for 2019-2020 and beyond.
Please Note: Files go into the Subsequent ISIR workflow only if the transaction is in a Verified status at the time the subsequent ISIR with unexpected changes is received. If the transaction status is in processing corrections, the file continues to go into Reviewing File status in the File Review workflow.
New Aid Year Reminders
The New Aid Year Reminder is a special communication template that schools can utilize that will send out a notification to a student when a new award year's ISIR has come in and contains student actionable tasks that need to be completed. Under normal circumstances, because the new award year's verification transaction won't be opened until the student logs in or the institution manually opens it, the basic reminder notification won't pick up these actions needing to be completed. This communication supplements the normal outstanding actions reminder.
Due to federal regulations around waiving verification, selective service, and drug eligibility requirements, some institutions choose to continue to verify a combination of these items while others may waive them. These settings allow an institution to control whether these comment codes should be included or excluded from the list of actions to trigger this communication.
- Verification: controls whether or not comment codes 170 or 171 can trigger the communication
- Selective Service: controls whether or not comment codes 030, 033, or 057 can trigger the communication
- Drug Eligibility: controls whether or not comment codes 053, 054, or 056 can trigger the communication
- If the student has comment code 171 only and the switch is enabled - will trigger notification to student
- If the student has comment code 171 only and the switch is disabled - will not trigger notification to student
- If the student has comment codes 132 and 171 and the switch is enabled - will trigger notification to student
- If the student has comment codes 132 and 171 and the switch is disabled - will trigger notification to student (because comment code 132 would still trigger the notification)