Skip to main content
Three areas that describe what attests and what ends up in the attestation JWT: apps (the bundle IDs allowed to attest), claims (the custom claims minted into the token), and devices (what has actually attested).

Apps

Apps are addressable by bundle ID or UUID. The first app registered becomes the primary app; the primary app and the last remaining app cannot be deleted.

grantiva console apps list

List registered apps, primary first.
Needs apps:read.

grantiva console apps get

Needs apps:read.

grantiva console apps register

Register an app so devices running it can attest.
Bundle ID and Team ID are fixed at registration and cannot be changed afterwards. Needs apps:write.

grantiva console apps update

Rename an app or change its description and toggles.
Needs apps:write.

grantiva console apps activate / deactivate

Allow or stop accepting attestations from an app.
The primary app cannot be deactivated. Needs apps:write.

grantiva console apps set-primary

The app must be active. Needs apps:write.

grantiva console apps delete

Delete an app and everything attached to it.
Deleting an app removes its device profiles, flags, and attestation history. The command prompts on a TTY and requires --yes otherwise.
Needs apps:delete.

Custom claims

Custom claims are the extra values minted into each device’s attestation JWT. Claims are addressable by key or UUID, and evaluate in priority order — lower priority evaluates first. A claim key starts with a letter and contains only letters, digits, and underscores.

Claim types

Rules and configuration JSON can be inline or read from a file with @file.json.

grantiva console claims list

List custom claims in priority order.
Needs claims:read.

grantiva console claims get

Needs claims:read.

grantiva console claims create

The option matching the claim’s type is required: --type static needs --value, conditional needs --rules, dynamic needs --expression, external needs --external. That is checked before the request is sent. Needs claims:write.

grantiva console claims update

Change a claim’s name, description, priority, active state, or configuration.
The claim’s type, data type, and key are fixed at creation. Only the configuration option matching the claim’s type applies. Needs claims:write.

grantiva console claims reorder

Set claim priorities by listing every claim in order.
Every claim must appear exactly once; the first listed gets priority 0. Needs claims:write.

grantiva console claims delete

Needs claims:delete.

grantiva console claims test and preview

test evaluates a claim definition you have not saved; preview evaluates a saved claim. Both run against a simulated device.
Device options, shared by both: test takes the same definition options as create. Needs claims:test.

Devices

grantiva console devices list

List devices, most recently attested first.
Risk bands: low 0–20, medium 21–50, high 51–75, critical 76–100. Needs devices:read. Filtering by --app also needs apps:read to resolve the bundle ID.

grantiva console devices get

Show a device’s profile and its recent attestation events.
The argument is the device’s App Attest key ID. Needs devices:read.

Next steps