iam roles
tcloud iam roles
Organisation IAM roles, permission rules, and bindings
Synopsis
Custom organisation roles define permission rules and can be bound to users, teams, or service accounts. System roles may be read-only; the API enforces what you can change.
Options
-h, --help help for rolesOptions inherited from parent commands
--access-token string Access Token authentication (overrides context)
--api string API endpoint (overrides context)
--client-id string OIDC client ID for OIDC authentication (overrides context)
--client-secret string OIDC client secret for OIDC authentication (overrides context)
-c, --context string Context name
--debug Debug mode
--ignore-dir-config Ignore directory-local .thalassa defaults
-O, --organisation string Organisation slug or identity (overrides context)
-P, --project string Project identity (overrides context; slug is resolved to identity; use "root" for organisation scope)
--token string Personal access token (overrides context)SEE ALSO
- tcloud iam - Identity and access management for your organisation
- tcloud iam roles bindings - Role bindings (who receives the role)
- tcloud iam roles create - Create a custom organisation role
- tcloud iam roles delete - Delete a custom organisation role
- tcloud iam roles get - Show a role including rules and bindings summary
- tcloud iam roles list - List organisation roles
- tcloud iam roles rules - Permission rules on a role