Submit a Ticket

Loading support form...
Skip to content
  • There are no suggestions because the search field is empty.

uConnect IT Onboarding Technical Guide

Learn about our technical configurations for the uConnect platform, which include setting up SSO, DNS, email whitelisting, and automated student information data imports (SIS) or a manual student data import. 

This article covers everything your university IT team needs to set up and configure uConnect, including DNS and email deliverability, Single Sign-On (SSO), and student data integrations. Use this guide to understand requirements, timelines, and recommended steps for a smooth go-live.

IT support is critical to uConnect onboarding because the platform requires coordination across:

We recommend starting with DNS/Email, SSO, and a Subscriber List for rapid onboarding. SIS syncs can follow later without delaying go-live.

1. DNS & Email Deliverability

Purpose

uConnect requires two types of DNS updates: (1) a CNAME record to point your institution's branded domain to the uConnect platform, and (2) email authentication records to ensure emails are delivered without being flagged as spam. uConnect will send your IT team customized DNS instructions with your platform's specific subdomain and sending email address. The records below are illustrative examples — your actual values will differ. See the full email setup guide for details.

Required DNS Updates

Primary Platform URL (domain pointing):

sitename.school.edu.   300   IN   CNAME   uconnectrootname.hosting.gouconnect.com

Email Domain Authentication:

uctreturn.schoolurl.edu.        300   IN   CNAME   u14324023.wl024.sendgrid.net uct._domainkey.schoolurl.edu.   300   IN   CNAME   uct.domainkey.u14324023.wl024.sendgrid.net uct2._domainkey.schoolurl.edu.  300   IN   CNAME   uct2.domainkey.u14324023.wl024.sendgrid.net

SPF Record Update:
Add the following IP to your domain's SPF record:

ip4:168.245.25.116
Email Tracking Links

Email link branding records are no longer required. Tracking links in uConnect emails use uConnect's secure address, links.gouconnect.com, over HTTPS, with no DNS changes needed on your end.

  • Already have link branding records? If your institution previously added uctlinks.schoolurl.edu or 14324023.schoolurl.edu records, please leave them in place. Emails sent before October 1, 2026 still rely on them, so removing these records could break tracking links in historical emails.
  • Want tracking links on your own domain? This is available on request and requires three DNS records. Submit a support ticket and we'll provide the exact values.
Email Allowlisting

uConnect Support emails come from our support systems, Intercom and HubSpot. To keep these emails and other uConnect communications from being flagged as spam, please ask your IT team to allowlist the following domains:

  • intercom-mail.com
  • spe.intercom-mail.com
  • gouconnect.com
  • hs-inbox.com

If your email security system requires IP addresses, use the values below:

Hostname IP Addresses
intercom-mail.com 3.162.112.42

USA: 34.231.68.152, 34.197.76.213, 35.171.78.91, 35.169.138.21, 52.70.27.159, 52.44.63.161

Europe: 54.217.125.63, 54.246.173.113, 54.216.9.3

Australia: 52.63.36.185, 3.104.68.152, 52.64.2.165
gouconnect.com 100.24.196.46
hs-inbox.com 141.193.184.64/26, 141.193.185.128/25, 18.208.124.128/25, 141.193.184.128/25, 141.193.185.64/26, 158.247.16.0/20, 3.93.157.0/24, 108.179.144.0/20, 54.174.60.0/23, 143.244.80.0/20, 54.174.59.0/24, 54.174.63.0/24, 3.210.190.0/24, 141.193.184.32/27, 54.174.52.0/24, 139.180.17.0/24, 141.193.185.32/27, 54.174.57.0/24

 

Tip: Platform emails (automated and custom emails) are sent through SendGrid from the IP address in your SPF record above. If platform emails are being filtered, your IT team may also need to allowlist that IP.

2. Single Sign-On (SSO)

Purpose

SSO allows students, faculty, and staff to log in to uConnect using their university credentials, improving security and user experience. Learn more here.

Supported Protocols

  • Primary: SAML 2.0
  • Other protocols: Supported on request (requires technical review)
  • SSO-supported tools: Shibboleth, Azure/Microsoft, Okta

Standard SAML Attributes

The standard SAML attributes table is currently being finalized. In the meantime, please contact uConnect Support for the latest required and optional attribute mappings, or refer to your implementation guide. At minimum, uConnect requires a unique user identifier attribute (matching your SSO login value) and an email attribute.

Process

  1. New setup:
    • uConnect provides Service Provider (SP) metadata.
    • Your institution provides Identity Provider (IdP) metadata.
    • Configure SSO only after DNS branding is complete. The final platform domain must be live before uConnect can generate accurate Service Provider (SP) metadata — if SSO is configured before this step, the SP metadata will need to be regenerated.
  2. Testing:
    • Test with IT and security staff.
    • Provide a test account if troubleshooting is needed.
  3. Updates:
    • Submit a support request if you need to modify SSO after launch.

 

3. Student Subscriber List (Manual Upload)

Purpose

Subscriber lists enable career centers to proactively send tailored content to students, alumni, employers, and staff. For onboarding, we start by uploading a current student subscriber list.

Recommended for Launch

Use a subscriber list for quick onboarding while SIS is being configured. Career center teams can upload these lists on their own. Learn more here.

File Requirements

FIRST_NAME, LAST_NAME, EMAIL, USER_ID (or USER_LOGIN if SSO), GRADUATION YEAR

Audience Types

  • Multiple subscriber types can be included in one file (e.g., students and alumni).
  • Include a SUBSCRIBER_TYPE column if you're mixing groups.

Optional Fields

  • Community pre-subscriptions (e.g., Career Community = Finance)
  • Multiple values are allowed when separated by ;

Upload Process

  1. Navigate to Engage > Subscribers > Manual Subscriber Uploads.
  2. Upload your file for processing.

 

4. Automated SIS (Student Information System) Integration

Purpose

The Automated SIS Integration keeps user records in uConnect in sync with your university's Student Information System (SIS). When students enroll, graduate, or change programs, their uConnect profiles are updated automatically — eliminating the need for manual uploads. Learn more about our SIS process.

Process

  1. uConnect provisions an Amazon S3 bucket.
  2. Your institution uploads a student list (CSV, RFC 4180 standard).
  3. uConnect reviews the file and enables auto-sync.

File Requirements

Required headers:

FIRST_NAME, LAST_NAME, EMAIL, USER_ID (or USER_LOGIN), GRADUATION, STAKEHOLDERS

Additional Notes

  • The unique identifier must match the SSO attribute.
  • Include one record per user (no duplicates).
  • Optional fields include EMAIL_OPT_OUT, DELETE, PROGRAM, AFFINITY, and more.
  • Academic programs and majors can be mapped to Communities (Career/Industry, College, Affinity).
  • Sync frequency: Weekly (Saturday nights)

5. Best Practices & Recommendations

  • Start with DNS, email, SSO, and a subscriber list to go live faster.
  • Set up SIS sync later, once configuration and mapping details are finalized.
  • Coordinate early with IT Security to address institutional policies.
  • Test thoroughly after DNS and SSO changes, before going live.
  • Provide test accounts when troubleshooting with uConnect.