Skip to content
Integrations/TriNet/Connection Guide
Connection Guide

Connect TriNet Without Breaking the Audit Trail

Use this guide to connect TriNet or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryHuman resources
Checklist3 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect TriNet and make sure the first collection lands cleanly.

  1. 1
    Provide company_id in config (if required by your TriNet tenant).
  2. 2
    Authenticate using either access_token (Bearer) or client_id/client_secret (Basic).
  3. 3
    Validate by listing employees.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

access_tokenclient_idclient_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.