Documentation Index
Fetch the complete documentation index at: /docs/llms.txt
Use this file to discover all available pages before exploring further.
Manage Ravion service accounts for automation. Create API keys in Settings > Service accounts > select the account > Create API key, then use RAVION_API_KEY instead of a personal membership key.
ravion service-accountservice-accounts
ravion service-account assignable-rolesravion service-account assignable-roles [flags]
| Flag | Required | Description |
|---|---|---|
--action <string> | Create is the default. Update requires the service account being edited. Available values: create, update. | |
--json | emit response as JSON | |
--target-id <string> | Existing service account ID; valid only for update. | |
-v, --verbose | show full output |
ravion service-account createravion service-account create [flags]
| Flag | Required | Description |
|---|---|---|
--name <string> | yes | User-facing service account name. |
--description <string> | Optional context for what this service account is used for. | |
--json | emit response as JSON | |
--role <roles> | Deprecated: use roles. Writing it sets roles to this one role; it cannot be sent with roles. OWNER is accepted and sets platform-admin and operator. Reads return the service account’s role with the most access, or its first custom role. | |
--roles <platform-admin> | The roles the service account holds across the organization, each a system-managed role key (platform-admin, operator, manager, read-only or billing) or a custom role ID. It holds at least one, and cannot hold owner or a role that can delete the organization. Reads list system-managed roles in that order, then custom roles by name. Setting roles replaces the whole set. Roles other than platform-admin and operator require policy administration to be enabled for the organization, and the caller can add or remove only roles whose permissions it already holds. |
ravion service-account deleteravion service-account delete <id> [flags]
| Flag | Required | Description |
|---|---|---|
-y, --yes | skip confirmation prompt |
ravion service-account getravion service-account get <id> [flags]
| Flag | Required | Description |
|---|---|---|
--json | emit response as JSON |
ravion service-account listravion service-account list [flags]
| Flag | Required | Description |
|---|---|---|
--cursor <string> | cursor | |
--json | emit response as JSON | |
--limit <int> | limit | |
-v, --verbose | show full output |
ravion service-account updateravion service-account update <id> [flags]
| Flag | Required | Description |
|---|---|---|
--description <string> | Optional context for what this service account is used for. | |
--json | emit response as JSON | |
--name <string> | User-facing service account name. | |
--role <roles> | Deprecated: use roles. Writing it sets roles to this one role; it cannot be sent with roles. OWNER is accepted and sets platform-admin and operator. Reads return the service account’s role with the most access, or its first custom role. | |
--roles <platform-admin> | The roles the service account holds across the organization, each a system-managed role key (platform-admin, operator, manager, read-only or billing) or a custom role ID. It holds at least one, and cannot hold owner or a role that can delete the organization. Reads list system-managed roles in that order, then custom roles by name. Setting roles replaces the whole set. Roles other than platform-admin and operator require policy administration to be enabled for the organization, and the caller can add or remove only roles whose permissions it already holds. |
Was this page helpful?