Specifications include, but are not limited to: 2.1. Login and Registration. 2.1.1. Ability for professionals and students to register and provide information about their experience, interests and career/professional needs. 2.1.2. Compatibility with shibboleth SSO for student/admin login. 2.2. Directory and Mentoring Functionality. 2.2.1. Ability for users to set parameters around how, when and about what they are willing to engage with other users (e.g., topics they are interested in discussing, times they are contacted, ways they want to interact). 2.2.2. Searchable database of mentors, with robust search parameters. 2.2.3. Ability to facilitate student-to-student connections and alum-to-alum connections, as well as traditional student-to-alum (professional) connections. 2.2.4. Algorithm-driven recommendation of mentors to mentees. 2.2.5. In-platform connection/communication/scheduling tool that maintains the privacy of mentor contact information. 2.3. Administration and Data Management. 2.3.1. Open API and/or ability to synchronize data with Salesforce. 2.3.2. Robust reporting functionality and analytics 2.3.3. Robust administrative tools e.g., site management, customization of roles and permissions, ability to send bulk emails, ability to customize fields 2.3.4. Ability to meet the UO data security requirements. See Section 4.5 of this RFQ. 2.4. Design, Support, and User Experience. 2.4.1. Ability to incorporate University design elements, including color schemes, fonts, graphics and images. 2.4.2. Current/modern design and UI; simple and intuitive UX. 2.4.3. Robust customer support with a quick response rate and dedicated account manager.