Compliance Hub for training providers
Training providers can connect completed training to an ongoing employer record workflow through API ingestion, document upload, and trusted partner single sign-on. Integration details can be discussed without exposing private partner identities or credentials.
The operational problem
A training purchase may end with a certificate download while the employer still needs to assign the record, retain the document, monitor expiration, and make proof available later. Manual handoffs add repeated work for both providers and employers.
The product workflow
- Use an API key for permitted employee and certificate imports.
- Upload a training document and receive its public document code.
- Link document codes to the certificate record through the API.
- For approved trusted integrations, create a short-lived, single-use SSO launch token for the employer and user.
- Let the employer continue with expiration, reporting, and Compliance Card workflows.
Buyer questions
Does an integration require private credentials in a browser?
No. API credentials belong in the trusted backend. SSO launch tokens are opaque, short-lived, single-use, and scoped to the supplied employer and user.
Can the provider upload certificate documents?
Yes. The documented API workflow supports multipart document upload followed by certificate linking with returned document codes.