Organization settings
Settings in the sidebar footer covers everything organization-wide.Organization details
Your organization’s name and slug. The name is also what your JWTaud claim carries, and the lowercased name is what the default iss is built from — see Issuer and audience.
Notification preferences
Per-organization email toggles. Turning one off stops that email for everyone in the organization.Attestation failure-rate alert
Set a failure-rate threshold and Grantiva emails you when your attestation failure rate over the last hour exceeds it. The check runs every 15 minutes, only fires above a minimum attestation volume so a handful of requests can’t trip it, and has a 4-hour cooldown between alerts for the same organization.Danger zone
Deleting the organization requires typing its slug to confirm, and is restricted to the owner. It removes all associated data.API keys
API Keys issues server-to-server credentials for backend integrations — the analytics API, the CLI, flag and claim management. They are never for shipping in a client app.
Creating a key needs a name (up to 100 characters), at least one scope, and optionally an ISO-8601 expiry. The secret is shown once and stored hashed — there is no way to recover it later.
Scopes bound what a key can do, granted per area:
A key can only grant scopes its creator already holds. Rotate a key to issue a fresh secret while keeping its name and scopes; revoke to disable it permanently. Both are audited.
Audit log
Audit Log records every security-relevant action, newest first, searchable across the action name, the actor’s email, and the resource type. Actions are namedresource.verb.
Entries carry the actor, the resource type and id, and action-specific metadata — the email on an invite, the old and new tier on a billing change, the URL on a webhook change.
Read the log through the audit log API as well as the dashboard.