What does CI need to upload audits?

CI needs the CLI command, repository context, and a scoped upload token stored as a secret.

Can CI uploads be reviewed later?

Yes. Processed audits remain visible according to plan limits and retention.

Guide

Turn CI audit output into review history.

A CI workflow can produce audit bundles, upload them with a scoped token, and leave the dashboard to handle review, provenance, and plan usage visibility.

Create account Open GitHub Actions docs

Prepare workspace setup

Create the organization, repository, and upload token from the dashboard. Store the token in your CI secret store rather than in source control.

Upload with context

Include repository slug, branch, and commit SHA in the upload command so reviewers can tie audit data back to a concrete build.

Review and scale

Use billing meters to understand repository, upload, seat, and retention limits as CI adoption expands.

CI risk dashboard Quickstart Plans

FAQ

Should CI use a user login?

No. CI should use a scoped upload token created from dashboard setup.

What if an upload fails?

Operations screens show recent processing failures and retry context where available.