# Commercial features

> Custom roles, release approvals, finding waivers, single sign-on, directory provisioning, audit export and model-assisted review. What each does, and the edition and plan that it needs.

Source: https://skaas.io/docs/commercial-features
Last updated: 2026-11-15

These features live in the `ee/` directory of the repository, under a commercial license. They run in the hosted service on the plans below, and in a self-hosted deployment that holds a commercial license. The Community edition does not include them.

Cloud Business is listed but not sold yet, and Enterprise is by contract. The pricing page shows the current state. A feature that a plan does not have answers a request with `PLAN_LIMIT_EXCEEDED`, and the dashboard says that the plan lacks it.

## Which feature needs which plan?

| Feature                       | Plan feature key   | Permission to use it                     | Cloud plans          | Self-hosted        |
| ----------------------------- | ------------------ | ---------------------------------------- | -------------------- | ------------------ |
| Custom roles                  | `custom_roles`     | `role:manage`, `role:assign`             | Business, Enterprise | Commercial license |
| Release approvals             | `approvals`        | `approval:grant`, `approval:revoke`      | Business, Enterprise | Commercial license |
| Finding waivers               | `policy_waivers`   | `audit:waive`                            | Business, Enterprise | Commercial license |
| Single sign-on                | `saml`             | `sso:manage`                             | Business, Enterprise | Commercial license |
| Directory provisioning (SCIM) | `scim`             | `scim:manage`                            | Business, Enterprise | Commercial license |
| Read audit trail and export   | `read_audit_trail` | `audit_trail:read`, `audit_trail:export` | Business, Enterprise | Commercial license |
| Model-assisted review         | `llm_review`       | `llm_review:manage`                      | Business, Enterprise | Commercial license |

Every administration call also needs the `repos:admin` scope on the token.

## Where do I find them in the dashboard?

Under **Settings** of the organization, each feature has its own page: Custom roles, Audit export, Model review, Single sign-on and Directory sync. A page that the organization cannot use says why, in one of three ways.

| What the page says                           | What it means                                                                                                                                                                                       |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "<Feature> is not in your plan"              | The plan lacks the feature. The page names the plan that has it and links to Billing and usage.                                                                                                     |
| "<Feature> needs a commercial license"       | The deployment is the Community edition and runs without a license. Whoever runs it adds the license, and the page then shows the feature.                                                          |
| "<Feature> is not set up on this deployment" | The feature is available, but the operator has not wired the service that it needs. The page says what to set, such as `SKAAS_ENCRYPTION_KEYS` for a stored key or the address of a graph database. |

The **Custom roles** page lists each role with its base and the permissions that a holder ends up with, and it has a form to create a role and a form to give a role to a member. A second table, **Who holds a custom role**, shows the holders: each person with the role that they hold, and the table of roles has a column **Held by**. The list comes from `GET /v1/orgs/{org}/role-assignments`, which returns every person with a stored role assignment, ordered by person. If the list does not load, the page says so and the rest still shows. The **Audit export** page asks for a first and a last day, shows the manifest of that period (the number of records, where the hash chain starts and ends, and the seal), and then offers the download. The server limits a period to 400 days, and the download is read through the web application before it reaches the browser, so a long period takes a while. A deployment that holds no sealing key says that the manifest has no seal. The **Model review** page keeps the key and lists the reviews, and each review has a page with its findings. The **Single sign-on** and **Directory sync** pages follow the routes below.

## What are custom roles?

Four built-in roles exist: owner, admin, member and viewer. A custom role extends one of the last three with a set of permissions. It holds the permissions of its base, plus the ones you add, minus the ones you remove, and it can carry a default grant level on every repository of the organization. Two permissions are owner-only, deleting and transferring the organization, and no custom role can hold them, so an organization always has an owner.

There are 26 permissions, each written `<area>:<action>`, such as `repo:publish`, `skill:quarantine`, `audit:waive` and `token:create_service`. Create a role with `POST /v1/orgs/{org}/roles`, and give it to a member with `PUT /v1/orgs/{org}/members/{user_id}/custom-role`. A role has a revision that counts up, so two administrators cannot overwrite each other without noticing. A person who leaves the organization loses their custom role, and a later return does not bring it back.

## What are release approvals?

A repository can require approval, and it can ask for more than one reviewer, from 1 to 10. A release then enters a snapshot only when enough different people approved that exact release. An approval counts only when:

- it is about that release hash, in that repository, for every channel or for the channel in question;
- it is not revoked;
- its reviewer is a person other than the one who published the release;
- the audit evidence that it carries did not say `blocked`.

A person counts once, however often they approve. A release published by a service key has no publisher to exclude. A release published through a token that cannot be traced to a person cannot be approved: the approval is refused. Approve with `POST /v1/releases/{release_id}/approvals` and revoke with the matching revoke route. A revocation takes effect from the moment the store has it.

## What are waivers?

A waiver accepts one finding for a limited time. See [the audit and its limits](/docs/auditor) for the default roles and durations, and for the admin access to the repository that every waiver needs on top of them. Waive with `POST /v1/audits/{audit_id}/findings/{finding_id}/waive`, with a reason and an expiry. The waiver and its event are written together, so the log never misses one. A finding that was waived and whose waiver ended is open again, and the log records the end.

## What does single sign-on cover?

You register an identity provider for your organization, either OpenID Connect or SAML, and name the email domains it speaks for. You prove each domain with a DNS TXT record, which the registration returns, and then ask SKaaS to check it. An organization can register up to five providers.

Enforcement is a separate switch. When you turn it on, people with an address in a verified domain must sign in through the provider, and their other sessions end unless you say not to. Owners may still sign in without it, so a broken provider cannot lock everyone out. A first sign-in through the provider creates the person as a member. No sign-in can create an owner.

## What does directory provisioning do?

SCIM lets your directory add and remove members. Create a directory token, with an expiry and the scopes you want, and give the directory the base path `/scim/v2` on your API host. A person that the directory adds counts against the seats of your plan, and a directory that asks to add one more than the plan allows is refused and the refusal is recorded. A directory that asks to remove the last owner is refused too, because the owner stays. A removal by the directory takes the same path as any other removal.

## What is in the audit export?

One file of the events and the reads of a period, at most 400 days, as JSON Lines or CSV. Ask for it with `GET /v1/orgs/{org}/audit/export?from=...&to=...&format=jsonl`. Each record has the same 17 columns: the record type, id, time, organization, action, actor, target, repository, skill, release hash, how the read arrived, the tool, the size, the request id and the details.

The export masks anything that looks like a secret and drops details with a telling name, and the manifest counts the masks. A CSV cell that could run as a formula in a spreadsheet gets a leading apostrophe.

A hash chain runs over the lines as they leave. Each value is the SHA-256 of the previous value, a line break and the line itself. The first value is bound to the organization, the period and the format. The manifest, which you read from `GET /v1/orgs/{org}/audit/export/manifest`, holds the first value, the last value and a checkpoint every 1,000 records. A changed, missing, added or swapped record changes the last value. This is how to check it.

```js
import { createHash } from "node:crypto";
import { readFileSync } from "node:fs";

const sha256 = (text) => createHash("sha256").update(text).digest("hex");
const manifest = JSON.parse(readFileSync("manifest.json", "utf8"));
const text = readFileSync(`export.${manifest.format}`, "utf8");

// JSON Lines ends each record with a line feed. CSV ends each record with a carriage return and a
// line feed, and its first line is the header, which is not part of the chain.
const lines = text.split(manifest.format === "jsonl" ? "\n" : "\r\n");
if (lines.at(-1) === "") lines.pop();
if (manifest.format === "csv") lines.shift();

let value = manifest.chain.genesis;
for (const line of lines) value = sha256(`${value}\n${line}`);
console.log(value === manifest.chain.head ? "intact" : "changed");
```

The file name in the sketch is only an example: use the name you saved the export under. A manifest that the exporter sealed with a key also carries an HMAC over the rest of it, which shows where it came from. The export needs the `read_audit_trail` feature. The retention of the plan limits how far back it reaches.

## What is model-assisted review?

A model reads the guide and the scripts of a release and reports findings, each with a quote from the file as evidence. Use it for the intent that a pattern cannot catch, such as a guide that asks an assistant to quietly send a file somewhere.

You bring your own key, for Anthropic or for an OpenAI-compatible endpoint. The key is sealed with the deployment's encryption keys, and only its last four characters are shown again. Add it with `PUT /v1/orgs/{org}/llm-review/key`, and start a review of a release with `POST /v1/releases/{release_id}/llm-review`.

The text of the release goes to the provider that you chose, so use a provider that you may send it to, and keep secrets out of skills. Secrets that appear in a finding are masked before it is stored. A finding survives only if its quote appears in the file, is long enough to mean something and is not a duplicate, so an invented finding is thrown away. At most 50 findings are kept. A finding from the model never blocks a release on its own. A finding at Medium or above raises a review for a person to decide. A model can miss what a pattern would catch and can be wrong in both directions, so treat its report as one more signal.
