A Teams seat is Pro for the person plus a shared workspace for the organisation. This is what the workspace contains.
One standard for the organisation, built in the workspace Config Studio and committed beside the code.
Repositories report their audits into the workspace, each keeping its own findings, dependencies, and trend.
Health score, files scored, and pushes blocked across the organisation, with the delta against the previous period.
A daily signal chart, the longest active streak, and the mix of what your team actually ran.
Every recorded event, filterable by signal, showing who ran what and under which version of the policy.
An exportable report with per-project tables, for the review that happens outside the tool.
Owner, admin, and member roles, invitations with expiry, and a seat limit the workspace enforces.
Seats billed to the organisation at your region's resolved rate, starting with a 14-day trial.
Analysis still runs on each developer's machine. What reaches the workspace is the outcome of a run and the counts that came out of it.
Team evidence records execution outcomes and aggregate counts. It never contains source, file paths, repository URLs, snippets, or finding text.
Never leaves the machineA 14-day trial starts when the workspace is created, with no card. Seats are billed monthly to the organisation from a minimum of 3.
Name it, take the generated URL, and the trial starts on creation. Invitations can wait.
Build it in the workspace Config Studio, preview it read-only, then commit the .irisconfig.json beside the code.
Each repository reports its audits into the workspace, and every project gets a trend instead of a one-off number.
Owner, admin, and member roles, invitations with expiry, and a seat limit the workspace enforces.