The district-level System Preferences tool allows districts to configure settings for general use of Infinite Campus. These preferences should only be modified by a district administrator, as modifications will affect system operations. Additional preferences may be contained within the module to which they relate.
District-Level System Preferences
The following table outlines the available options for each preference and the area of the product it affects. When applicable, click on the name of the preference in the table to view additional information.
System Preference
Definition
Area(s) Affected
Campus Edition
Search Screen Field Order
The Search Screen Field Order system preference determines where the Student Number field will be located in relation to name fields when conducting an Advanced Search for students.
The Search Screen Field Order system preference determines where the Student Number field will be located in relation to name fields when conducting an Advanced Search for students.
Search Screen Field Order
The available options have the following implications:
Student Number AFTER Name Fields -- The Student Number field will display as the third field on the Advanced Student Search screen.
Student Number After Name Fields
Student Number BEFORE Name Fields -- The Student Number field will display as the first field on the Advanced Student Search screen.
This preference determines how multiple enrollments in the same school year are handled within Campus. These settings are enforced when managing enrollments from anywhere within Campus (Student Enrollment tab, Census Enrollment tab, Student Locator, etc.).
Centralized Enrollment: Auto-End Overlapping Primary Enrollments. This option automatically enters an End Date for the old primary enrollment when a new overlapping enrollment is created. This date is the date before the Start Date of the new enrollment record. When a new non-primary enrollment has the same date as another primary enrollment, both enrollments remain active. If the start dates are the same, a message displays indicating the primary enrollment cannot overlap with another primary enrollment. The existing enrollment ends with the entered start date and is set to No Show.
Decentralized Enrollment: Allow Overlapping Primary Enrollments. Allows primary enrollments to overlap. Red exclamation points will display next to the overlapping enrollments on the Enrollments tab.
Overlap Warning: Auto-end overlapping primary enrollment. Warn the user. Warns the user when a new primary enrollment overlaps with another primary enrollment. The user may click OK and continue creating the enrollment. The new enrollment's start date is compared to any existing enrollment's start date. If the start dates are the same, a message displays indicating the primary enrollment cannot overlap with another primary enrollment. The existing enrollment ends with the entered start date and is set to No Show.
Strict Prevent and Warn Primary: Prevent overlapping of primary enrollments in any calendar. Warn the User. Allow secondary enrollment overlaps. This option prevents the overlapping of primary enrollment records in any calendar. A warning appears when the user attempts to create a new primary enrollment which overlaps another primary enrollment. The enrollment will not be saved and selecting OK on the warning message will result in an error displaying.
This option DOES NOT allow partial enrollments to exist without there already being a primary enrollment. This prevents the ability to have two enrollments in the same calendar, even if the enrollments are in separate schedule structures and even if the enrollments are varying service types (primary, secondary, etc.). This option DOES NOT prevent the creation of a new Primary enrollment that overlaps a No Show enrollment.
Strict Prevent and Warn Non-Primary: Prevent any primary enrollment overlap in any calendar, allow Non-Primary Enrollments with no primary enrollment. This option prevents primary enrollments from overlapping in any calendar, but non-primary enrollments can overlap if there are no primary enrollments.
This prevents the ability to have two enrollments in the same calendar, even if the enrollments are in separate schedule structures and even if the enrollments are varying service types (primary, secondary, etc.). This option DOES NOT prevent the creation of a new Primary enrollment that overlaps a No Show enrollment.
Maine Users ONLY: The Enrollment Overlap Behavior preference will not affect non-Primary enrollments.
This applies to both State and District Editions of Campus
Enrollments where Service Type = N: Special Ed Services may also overlap regardless of System Preferences.
Indicates which end status is automatically assigned to enrollments when enrollments are ended.
This preference only appears when the Enrollment Overlap preference is set to the following:
Centralized Enrollment.
Overlap Warning: Auto-end overlapping primary enrollment. Warn the user.
Prevent and Warn: Allow 1 day of overlap. Prevent more than one day of overlapping primary enrollments. Warn the user (only available for Louisiana districts)
This preference is used when mapping local enrollment start statuses to state start status.
When set to User Maintained, no auto-maintenance process occurs with Campus and users (districts) are expected to manually create all necessary enrollment start status mappings.
When set to Campus Maintained, the auto-maintenance process occurs within Campus and users (districts) do not need to manually create enrollment start status mappings. This is the default selection.
When Campus Maintained is selected, a trigger is placed on the Start Status table any time a new state start status is added to the Attribute/Dictionary (by a user or by Campus). A mapping record is created with the following information:
Start School Year as the currently active school year. If an active school year is not selected, the current year is used (for example, if the current year is 2020, the Start School Year is set to 19-20 school year).
End School Year as the currently active school year
Code for the new State Start Status code
Name for the new State Start Status code
Mapping for the new State Start Status code
Text to indicate the mapping was created during the conversion process, and a date/time stamp
When a State Start Status is inactivated in the Attribute/Dictionary, the School End Year is automatically set to the Active Year.
When a State Start Status is re-activated in the Attribute/Dictionary, the School End Year is removed.
Duplicate codes can be created, but the saving of duplicate codes is not allowed. Users need to modify the duplicate code or delete it.
This preference is not available for South Dakota or Montana LDE districts.
This preference is used when mapping local enrollment start statuses to state start status.
When set to User Maintained, no auto-maintenance process occurs with Campus and users (districts) are expected to manually create all necessary enrollment end status mappings.
When set to Campus Maintained, the auto-maintenance process occurs within Campus and users (districts) do not need to manually create enrollment end status mappings. This is the default selection.
When Campus Maintained is selected, a trigger is placed on the End Status table any time a new state end status is added to the Attribute/Dictionary (by a user or by Campus). A mapping record is created with the following information:
Start School Year as the currently active school year
End School Year (not populated)
Code for the new State End Status code
Name for the new State End Status code
Mapping for the new State End Status code
Text to indicate the mapping was created during the conversion process, and a date/time stamp
When a State End Status is inactivated in the Attribute/Dictionary, the School End Year is automatically set to the Active Year.
When a State End Status is re-activated in the Attribute/Dictionary, the School End Year is removed.
Duplicate codes can be created, but the saving of duplicate codes is not allowed. Users need to modify the duplicate code or delete it.
This preference is not available for South Dakota districts.
If set to 'Yes', the Impact Aid tab and Impact Aid Site field on the Address editor display. These fields are used to report Impact Aid information in the Impact Aid and Military Connections Site and Impact Aid Employment Reports.
If set to 'No', the Impact Aid tab displays with a message indicating the preference is not turned on. The Impact Aid Site field on the Address editor does not display.
The Search Limit system preference allows districts to limit the number of results returned by a search to improve search and system performance.
The Search Limit preference has several levels of search limits: 100, 500, 1000, 3000, 5000 and No Limit. Once saved, the limit will be applied to the search results displayed on the Search tab.
This limit does not affect generated batch reports. For example, if the limit for searching for students is set to 100 and an Ad hoc filter contains 150 students, all 150 students will be included in the batch report.
In the interest of search response time and system performance, Infinite Campus does not recommend setting the "No Limit" option.
Exceeding Search Limits
If a system preference has been set, search results exceeding the limit set in the Search Limit field, red warning text will instruct the user to enter additional criteria that will return a smaller set of search results:
If set to 'On', users will receive a warning when attempting to enroll a student in a school outside of the student's geographical boundary.
The School Boundary Warnings preference validates the student's primary address against the chosen school of enrollment. The warning does not stop the enrollment from being created, rather it's an indication that the student's primary address is outside of the enrollment boundaries for normal enrollments. District policy may require additional proof of residence or a student's need to be enrolled in the selected school.
Having this preference on is recommended in larger districts that have multiple elementary schools, middle schools or high schools. If a larger district also uses a Centralized Enrollment process, this preference is also helpful in managing student enrollments.
School Boundaries settings on the Household Address need to be established prior to enrolling students.
School Association with Household Address
When the preference is set to On, a warning message displays when enrolling a student into a school that is not associated with the student's household address.
When the preference is set to Off, no warning displays when enrolling students, no matter if the Schools of enrollment have been associated with the address.
When the Require Student Assignment checkbox is marked on the Calendar and this preference is set to On, an enrollment cannot be saved for a student if the student's address is outside of the entered school boundaries, unless an override type is established that allows the enrollment to occur.
Indicates how many significant decimals (decimals to the right of the period) are allowed for GPA values.
No specific path
District State
Require all scores for Composite Grading
If set to 'Yes', teachers are not able to post a composite grade until the child grades that make it up have also been posted. This preferences takes roster start and end dates into account for students who were not enrolled in the section for the full time covered by the composite setup.
This preference causes a Bypass Composite Rule checkbox to display in the Score Groups and Rubrics. When marked for a grade, tasks with that grade are excluded from composite calculation.
When set to Yes, students may be assigned the same state ID number.
When set to No, each state ID number must be unique; if a duplicate ID is entered, an error message displays.
For districts that are part of a State Edition where state IDs are auto-generated, a value of Pending displays when adding a new student in the State ID field. This applies to the following states:
Kentucky
Maine
Montana
South Dakota
If a state ID import is used, duplication could still occur. The preference does not prohibit an import from importing a duplicate ID. This is the responsibility of the state to ensure IDs are not duplication.
The Student State ID Method system preference determines how Student State IDs are generated for new students within Campus.
This is only available for districts linked to a state edition.
For State-linked districts, the Student State ID Method field indicates how Student State IDs are assigned to new district students.
This field is likely to be set to a value of "State Assigned," meaning Student State IDs are generated by the state, in the format indicated by the state value. Any district-level Student State IDs will be overwritten by the state-level value (if discrepancies exist).
If the field is set to a value of "Generation Off," Student State IDs are not automatically generated and instead manually entered via the Demographics tab. Enrollment records created through the Student Locator will not automatically assign a Student State ID but will provide the user with the option to manually enter an ID (if known). Student State IDs created at the district level will sync up to the state
The Enable Student Assignment Validation is used in the School Assignment Process (School Choice). This preference works in conjunction with the School Boundary Warnings and the Enable Sequential School Choice Applications preferences.
When turned on, a student needs to reside within the boundaries of the chosen school or have an Override indicating the student can be enrolled in the school.
Setting this preference to Yes also requires the School Boundary preference to be set to Yes. When this is turned on, the schools assigned to the Schools tab within the address need to be marked as the Resides school.
When this preference is set to yes, the following logic is used in the Enrollment Roll Forward tool:
Continuous programs - If the student is participating in a continuous program and the current school does not offer the next grade, rather than mapping the next school from the school boundary table the processing will map the next school based on the program boundaries for the continuous program. If there is no mapping in the program boundaries that offers the next grade, then the student will roll using the school boundaries.
Next grade level in same school - When student assignment is used the roll forward will ensure that the student is within school boundaries. If the student has an override to attend the school for a program that requires program boundaries, the roll forward will also ensure that the student is within the program boundaries. If the student is outside program boundaries or school boundaries and does not have an override that would allow the enrollment the student will be rolled into their next calendar using school boundaries processing.
Promotion to new building based on School Boundary mapping - With student assignment a student may have a cluster of schools within their school boundaries that all offer the same grade level, however one of those schools will be marked as the Resides school. The student is allowed to attend any of those schools that are within their boundary, however the Resides school will be the default when rolling along school boundary mappings.
Destination Calendar and grade on the options page - Specifying a destination calendar/grade is only allowed for calendars and/or grades that do not require student assignment.
No specific path
District
Enforce Enrollment Attendance Zoning
When the preference is set to Yes, an error displays if the user saves a student enrollment and the student enrollment does not reside within the school boundaries associated with the student's household address(es) and the Variance Date and/or Variance Code are not entered.
This option is only available to districts in Nevada and Georgia.
Enable Sequential School Choice Application Processing
This preference processes a student's applications for school enrollment in an orderly fashion, based on the student's ranking of desired schools as part of the School Choice process. When this preference is set to Yes, applications will be processed based on the student's first, second or additional choices for school enrollment.
School Choice allows a student to submit as many applications for school enrollment as necessary, or as the student/parent is willing to submit. Using this preference ranks the applications based on the student's preferences and desires.
Use this in conjunction with the Enable Student Assignment Validations and School Boundary Warnings preferences.
Processing applications using the Process Application Wizard will only process approvals for the highest priority of a student's application.
No specific path
District
Staff State ID Generation
When set to On, a state ID generates for staff. When set to Off, no state ID generates for staff.
If set to 'Yes', provides users a warning in the Walk-In Scheduler when deleting or end-dating a course if the action results in a gap in the student's schedule.
Flag Health Conditions system preference determines the display of health conditions assigned to students. When set to yes, any condition marked as flagged will appear as checked by default when that condition is assigned to a student and the flag will appear by the student’s name. If this preference is turned off, the flag will not display next to the student’s name even if the box is checked in the Condition for the student.
When the Flag Health Conditions is set to Yes, a flagged condition marked on the Condition List that is assigned to a student will display an EMT symbol next to the student's name. This allows other staff who have that student in a class or are part of the student's learner plan team can see this condition and be aware of certain situations that may be difficult for that student.
When the Flag Health Condition is set to No, the EMT symbol will not display next to the student's name, even if a condition is flagged in the Condition List or if the condition is marked as flagged when assigning that condition to a student.
Default Health Conditions preference will allow users to use the Campus default conditions in addition to their custom conditions, or just the custom conditions.
No - When the preference is set to No, only custom health conditions display.
ICD-9 Conditions - When the preference is set to ICD-9 Conditions, the ICD-9 health conditions along with custom health conditions display.
ICD-10 Conditions - When the preference is set to ICD-10 Conditions, the ICD-10 health conditions along with custom health conditions display.
ICD-10 Health Conditions became the standard set of health conditions on October 1, 2015. See the Community News article for more information.
The Require Employment Record for District Assignment preference requires staff members to have a District Employment record before having a District Assignment record.
Districts that are not state-linked can modify this preference, as desired.
State edition customers and state-linked districts will not have the option to modify this preference. The preference will be determined by the state Department of Education and updated by Infinite Campus. The setting will be view/read-only in those situations.
This preference is enabled for users in Maine.
A corresponding District Employment Record is defined as such:
The start and end dates for the District Assignment must match or fall within the dates of a single District Employment Record.
A District Assignment record cannot end after the latest District Employment End Date.
A District Assignment record cannot start before the earliest District Employment Start Date.
A validation will occur when a District Assignment Record is created without the existence of a District Employment Record.
This preference does not apply to customers using the Human Resources module. The Human Resources module always requires staff to have a District Employment record before having a District Assignment record. (District Assignments are called Work Assignments in the Human Resources module.)
Employment Record Set to Yes
A District Assignment record cannot be created/edited/saved unless there is a corresponding District Employment record.
When ending a District Employment record, all District Assignment records in a district will be automatically ended if there is no other District Employment record in the district that can completely contain the Assignment.
For example, if there is a District Employment record that begins January 1 with no end date, and a second District Employment that begins February 1 with no end date and a District Assignment record that begins January 15 with no end date, the first District Employment record, when ended, will end the District Assignment record, because the remaining District Employment record cannot fully contain that assignment as it started prior to that record.
If the district assignment starts AFTER the District Employment record ends, the assignment will not be ended. The user will need to correct this situation in order to end the employment record by doing one of the following:
Changing the end date of the employment record to be later than the start date of the latest assignment
Deleting the assignment
Changing the assignment start date to be earlier than the employment end date
Employment records cannot be deleted if there is a corresponding District Assignment unless there is another Employment Record in that district that can contain all district employments. The following error message will appear if (1) there are district assignments in that district, and (2) there is no other district employment that can contain the district assignments.
When a District Assignment record exists after the end of its associated District Employment record, the following validation will occur, asking the user to correct the date issue.
When an employment record is saved and end date is entered, validation will occur to verify no District Assignment records start after the entered end date.
Employment Record Preference Set to No
When the District Employment Record preference is set to No, the staff person may have a District Assignment record without having a District Employment record.
When the District Employment record is saved and an end date is entered, the same alert message will display. If the user chooses to continue, only those assignments that start prior to the end date entered will be ended.
My Data Impact
If a staff person requests a change to the District Employment or District Assignment, no validation will be done at the request level. Validation is done at the Request Approval level. The validations mentioned above are used and the request cannot be approved until the validation issues are resolved.
This setting indicates the type of person record in Campus for which race/ethnicity information is required.
Preference Logic
Any state or district will see no change in preferences unless a modification is made manually. All state-linked districts will have the option to change these preferences independent of State Edition settings.
For Maine users, preferences will be set by the state and will be read-only for both State Edition and District Edition users. State-linked districts cannot choose the values for these preferences independent of those set by the State Edition. The following selections will be made:
Race/Ethnicity Required for - Staff and Students
Require Race - Always
Require Race/Ethnicity Determination - Never
Staff Behavior
When any of the race/ethnicity fields are required for Staff, the following will be enforced:
When the Demographics page for an existing staff member is loaded, the appropriate race/ethnicity fields will be marked as required (red text and asterisk). The page cannot be saved until the required fields are populated.
If the user deleted the Staff IDs after loading the page for an existing staff member, the race/ethnicity fields are still required. The page will need to be saved without the Staff ID and WITH the race/ethnicity and then re-loaded to remove the race/ethnicity if desired.
When the Demographics page is loaded for a person who does NOT have either of the Staff IDs, the appropriate race/ethnicity fields will not be marked as required. However, if a Local or State Staff ID is entered, the page cannot be saved until the appropriate race/ethnicity fields are completed.
The Staff Locator will require completion of the appropriate fields.
The Add Person tool will not allow a Save operation if a Local or State Staff ID is entered.
Student Behavior
When any of the race/ethnicity fields are required for Students, the following will be enforced:
When the Demographics page for an existing student is loaded, the appropriate race/ethnicity fields will be marked as required (red text and asterisk). The page cannot be saved until the required fields are populated.
If the user deleted the Student IDs after loading the page for an existing student, the race/ethnicity fields are still required. The page will need to be saved without the Student ID and WITH the race/ethnicity and then re-loaded to remove the race/ethnicity if desired.
When the Demographics page is loaded for a person who does NOT have either of the Student IDs, the appropriate race/ethnicity fields will not be marked as required. However, if a Local or State Student ID is entered and the person does not have a Staff ID, the page cannot be saved until the appropriate race/ethnicity fields are completed.
The Student Locator will require completion of the appropriate fields.
The Add Person page will not allow a Save operation if a Local or State Staff ID is entered.
All People Behavior
When any of the Race/Ethnicity fields are required for All People, it will be enforced in the Student Locator, Staff Locator, Add Person and Demographics tools.
For Kentucky districts, this field is controlled by the state. Values set at the state level are pushed down to districts.
This preference setting indicates when race information is required, based on the answer to the "Is the individual Hispanic/Latino?" question on the Demographics tab.
Available selections for this option vary depending on the selection of the Require Race/Ethnicity Data For preference.
If the Require Race/Ethnicity Data For preference is set to No One, the Require Race Selection preference will be set to Never.
For all other settings of the Require Race/Ethnicity Data For preference, options for Require Race Selection are Only when Hispanic/Latino = No and Always.
For Kentucky districts, this field is controlled by the state. Values set at the state level are pushed down to districts.
The Enable Attendance Auditing system preference indicates whether the district is auditing student attendance records. Setting this preference to Yes requires a significant amount of data storage:
The following reports are available for auditing attendance records.
These reports are available to users (as long as tool rights are assigned) even when this preference is not set to Yes. If this preference is not turned on, data will not be included in the report.
Attendance auditing provides a completed history of attendance changes for compliance with electronic signature requirements and other state reporting obligations.
This preference can be turned on and off at any time. Data will only be stored for the time when it is turned on (set to Yes). Reports can still be generated when it is turned off, but only the data stored during the time it is turned on will be returned on the reports.
Texas districts: This is a read-only option set to 'Yes' and cannot be modified. This preference is critical for attendance auditing utilized by state reporting.
Kentucky districts: This preference and the attendance tracking reports are not available.
The Batch Queue Expiration Days field of the System Preferences allows a system administrator to specify the length of time a Batch Queue report should display on the Batch Queue and Admin Queue tools before it is deleted.
If reports should never be automatically deleted by the Batch Queue Maintenance task, this field should be left blank (null).
The value entered in the Batch Queue Expiration Days field should reflect the maximum number of days a Batch Queue report is allowed to display on the Batch Queue and Admin Queue tools. When a report exceeds the maximum number of days allotted by this field, it will be deleted by the automated Batch Queue Maintenance task executed by the Task Scheduler .
A Batch Queue / Admin Queue report will not be deleted if a user has manually designated otherwise it be spared from deletion per one of the following methods:
Keep Until I Delete Option - This is set when the report is set up and assigned to the Batch Queue by marking the Keep Until I Delete checkbox from the Batch Queue Reporting Options.
Report Never Expires - This is set in the Expires After and Never Expires fields of the Batch Queue Detail editor of the Batch Queue / Admin Queue tools.
View Expiration Dates on Reports
PATH: Ad hoc Reporting > Batch Queue; System Administration > Batch Queue Admin > Admin Queue
Depending on the setting indicated in the Batch Queue Expiration Days preference and the specific preferences set for a report, theBatch Queue / Admin Queue tools will display one of the following types of values in the Expires After field of the Batch Queue Detail editor:
No Expiration Configured
Expiration Date
Crossed-Out Expiration Date
No Expiration Configured
If a value of "No Expiration Configured" appears in the Expires After field of a report, either the report has not yet been generated or the Batch Queue Expiration Days preference does not contain an expiration value.
Expiration Date
If a date appears in the Expires After field of a report, it indicates the scheduled expiration date on which the report will be automatically deleted from the Batch Queue List editors of the Batch Queue / Admin Queue tools.
Crossed-Out Expiration Date
If a crossed-out date appears in the Expires After field of a report, the Never Expires checkbox should also be flagged, indicating a user has manually excluded the report from deletion on the scheduled Expires Date of the Batch Queue / Admin Queue. The report will remain in the queue until a user manually deletes it or removes the check from the Never Expires checkbox (in which case the report will be deleted the next time the Batch Queue Maintenance task runs).
The Auto-pay Fees with Surplus Balance preference will automatically pay any fee with surplus from another fee.
Set the Auto-pay Fees with Surplus Balance Preference
Set the Auto-pay Fees preference to either Yes or No.
Click the Save icon when finished.
When set to Yes, auto-pay will happen in the following scenarios:
When a deposit is created after adjusting a fee assignment where the total adjustments plus total payments is greater than the fee amount.
When part of a payment is voided on a fee assignment. This will auto-pay any other fees that may exist (but not the one where the payment was just voided).
When a new fee assignment is created when there is a surplus balance. This will auto-pay the newly created fee first and then any remaining surplus will be auto--paid to other fees.
A message will appear when making a payment for Students and Persons when a surplus exists alerting the office person the deposit will be applied to other fees.
The Auto Post Course Fees preference posts any course fees to the Student Fees tab automatically (after the Course Fee Wizard is used) when students are scheduled into a course section through the Walk-In Scheduler or the Roster Setup tool.
When set to Yes, course fees will auto-populate for students who are schedule through the Walk-In Scheduler or Roster Setup tools.
Auto-Post Course Fees Process
The posting of course fees is a three-part process:
Set the Auto-Post Course Fees preference to Yes.
Add a fee to a Course.
Run the Course Fee Wizard by course.
When the Course Fee Wizard Select Fees to Post section Posted for Terms is not zero, the fees will post for all students who are added to that course's section roster.
The Days to Flag Roster Additions system preference determines the length of time a student's name will appear in green color within a section roster in both the Instruction module and on Course Section rosters. This gives the teacher and any office staff an indication that the student is new to the section.
The default value for this field is 10 days.
This preference is based on calendar days.
Note the following:
This preference will determine the number of days the start date is green in roster views.
The roster start date is considered Day 0 of the roster flag time period. If the roster start date is in the past, a student may never display in green text.
If no roster start date has been entered for a section, the student name will not display in green.
Any students with a start date entered on a section roster will display in green font in the following areas for the specified number of days:
Module
Tool
Campus Instruction
Attendance
Attendance > Seating Chart and Lab Seating Chart
Positive Attendance
Grade Book
Posting by Task
Posting by Student
Roster
Student Groups
Seating Charts
Lockers
Scheduling
Course > Section > Attendance
Student name color is based on the entered effective date, not on the current date.
Course > Section > Roster
Course > Section > Grade by Task
Course > Section > Grade by Student
Course > Section > Roster Setup
Course > Section > Roster Batch Edit
Attendance
Classroom Monitor
Student name color is based on the entered effective date, not on the current date.
The NGA Cohort Years after NCLB system preference allows users to dictate how many additional years are available for selection when entering NGA Cohort End Year values on the student Graduation tab.
This preference allows users to choose what database to use when generating and creating Ad hoc Reporting Filters (using the Filter Designer Query Wizard and Pass-Through Query tools).
Users can select to query data from the Data Warehouse database (default selection) or the Live Site.
This preference only displays when the district has a Data Warehouse database available.
This preference allows you to enable, disable, or access Ed-Fi tools in Campus before syncing to the Ed-Fi system.
Yes = Ed-Fi functionality is enabled and Ed-Fi data will sync from Campus to the Ed-Fi system (if properly enabled via Ed-Fi Configuration tools).
Tools Only = You are able to fill out Ed-Fi fields (such as Ed-Fi ID) within Campus but this data will not sync to the Ed-Fi system until this field is set to Yes.
This is especially useful when setting up Ed-Fi IDs for students within a school or district so that data properly syncs between Campus and Ed-Fi prior to enabling it.
No = Ed-Fi functionality is not enabled for the district and users cannot access Ed-Fi tools within Campus.
Ed-Fi
District
Allow access to Student Number as PIN Features
This preference allows the POS admin to update the Set Student Number as PIN POS Preference and run the Set Student Number as PIN Wizard in update mode.
User Access to the New Look of Campus (Try New Look)
This preference controls whether the Try New Look of Infinite Campus toggle appears for all users, only Campus Instruction users, or no users.
When the Try New Look toggle is set to ON, the UI is replaced with a new look and feel containing all existing Campus tools along with numerous new features such as an intelligent search bar, the ability to create your own favorite tools menu, and more.
By default, this preference is set to ‘All Users’ for Campus Cloud and Cloud Choice customers.
Users who have turned the Try New Look toggle to ON can switch it to OFF at any time which will revert their Campus experience back to original Campus (Classic Campus).
Note for In-District and Self-Hosted Customers: This preference is not visible as the Try New Look UI is currently not available for these hosting models.
Determines how the value for the 'Duration in School Days' field for a Behavior Resolution is calculated when the Calculate End Date/Duration option is marked on a Resolution Type. Options are:
Standard: Calculates the 'Duration in School Days' field to the nearest whole number.
Detail: Calculates the 'Duration in School Days' field to the hundredths place.
This preferences allows student monitoring of English Learner services to be extended as a result of state changes (e.g., pandemic-related updates or testing delays).
When set to Yes, the student's EL tool displays a read-only Fifth Year Monitoring label. When set to No, this label does not display.
Cascade Enrollment End Date to Blended Learning Group Assignment End Date
This preference determines whether a student's Blended Learning Group Assignment is ended when the student's Enrollment record is ended. The Blended Learning Group will have the same End Date as the Enrollment record.
When set to Yes, once the enrollment record is ended, the Blended Learning Group assignment is also ended. If there are Blended Learning Group assignments beyond the enrollment end date, they are also deleted.
When set to No, the Blended Learning Group assignment is NOT ended when the Enrollment record is ended.
When set to No, this label does not display.
