Implementation roles
The following roles are generally required to implement Naviance:
|
IT project leader |
Responsible for all decisions related to the implementation and configuration of Naviance. Ensures deliverables and timelines are met. This individual typically serves as the primary client contact for the Naviance consultant, if services were purchased. |
|
Database administrator |
Responsible for exporting data from the student information system (SIS) to Naviance. Naviance provides documentation to ensure data files are in the proper format for a successful import into Naviance. |
|
Systems administrator |
Responsible for any configurations required for Naviance and Naviance Student, such as single sign-on (SSO) integration. Naviance provides documentation on how to set up SSO for students and staff. |
|
Developer |
Responsible for creating custom code or modifying jobs to configure and deploy Naviance products. Naviance consulting does not develop or perform custom code work. |
Technical requirements
The following TCP (Transmission Control Protocol) ports are used to access Naviance:
-
HTTP - TCP port 80 (automatically redirected to HTTPS - TCP port 443)
-
HTTPS - TCP port 443
Allowlist email accounts and domains
Ensure the following email accounts are allowed senders:
Allowlist the following domains:
Allowlist web content
Ensure Naviance and Naviance Student are not blocked by whitelisting the following:
|
Domain-level |
|
|
Individual site level |
|
|
Roadtrip Nation videos |
|
|
Videos |
|
|
Assessments |
|
|
College |
|
|
Partnership URLs |
Naviance does not support IP address allowlisting.