Articles in this section

Technical Admin Responsibilities Checklist

This checklist outlines the core responsibilities of a Technical Admin supporting Harvard Business Impact Enterprise products. Use it to understand what you own, what to monitor, and when to involve internal IT or Harvard Business Impact support.

 


 

Identity & Access Ownership

 

Technical Admins are responsible for how users authenticate and gain access to Harvard Business Impact platforms.

 

You own:

  • Identity provider (IdP) configuration and management
  • SSO/SAML maintenance
  • Submitting and/or monitoring user attributes (email, unique ID, roles)
  • Access rules and entitlement logic

 

You should validate:

  • Users can authenticate successfully
  • Attributes passed from your IdP are accurate
  • Role or access changes take effect as expected

     


 

Integration Maintenance

 

If your organization uses integrations, ongoing upkeep is required.

 

You own:

  • LMS, LXP, or HR system integrations
  • Integration credentials, keys, or certificates
  • Coordination with LMS and IT teams after system changes

You should monitor:

  • Integration success and failure indicators
  • Changes to upstream systems that could affect data flow
  • Updates announced by Harvard Business Impact that may require coordination

     


 

Data Accuracy & Testing

 

Technical Admins help ensure that user and activity data behaves as expected.

 

You own:

  • Initial testing during onboarding or changes
  • Verification of user creation and access
  • Spot-checking data flow and reporting outcomes

 

You should test after:

  • SSO or IdP changes
  • LMS or platform upgrades
  • Certificate rotations or attribute updates
  • Large user uploads or provisioning changes

 


 

Ongoing Monitoring & Issue Triage

 

Technical Admins act as the first line of diagnosis for technical issues.

You own:

  • Monitoring authentication and integration health
  • Identifying whether issues are internal or vendor-related
  • Collecting technical details before escalation

 

You should be prepared to gather:

  • Error messages or screenshots
  • Affected user details
  • Timestamps and recent system changes
  • Logs or diagnostic files when applicable

 


 

Where to Go Next

 

Once you understand your role, these resources can help you go deeper:

Was this article helpful?
0 out of 0 found this helpful