Lists every team (a personal account is a team of one) with your role: owner, admin, member or viewer. The current team is the one your token belongs to.
Usage
overlane team list [--service URL]Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--service |
string | no | The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service) |
Examples
overlane team listBehavior
- Effect:
read(changes nothing). - Needs credentials: yes. Uses the network: yes.
- Supports
--dry-run: no. Accepts--force: no. - Machine-readable description:
overlane schema team list.
Result
With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.
{
"type": "object",
"properties": {
"teams": {
"type": "array",
"items": {
"type": "object",
"properties": {
"tenantId": {
"type": "string"
},
"name": {
"type": "string"
},
"kind": {
"type": "string",
"enum": [
"personal",
"organization"
]
},
"role": {
"type": "string"
},
"current": {
"type": "boolean"
}
},
"required": [
"tenantId",
"name",
"kind",
"role",
"current"
],
"additionalProperties": false
}
},
"next": {
"type": "string"
}
},
"required": [
"teams",
"next"
],
"additionalProperties": false
}See exit codes for the status the process returns.