CLIorg
capxul org permission assign
Propose assigning one active Permission to one exact Account; you approve it in the browser
Runs in: devnet · staging · production · Moves money: no
Usage
capxul org permission assign [flags] [<id>]Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
<id> | string | no | The Permission ID |
Flags
| Flag | Type | Required | Description |
|---|---|---|---|
--email | string | no | the signed-in person to use, when this machine has several |
--account-id | string | no | the member's Account ID |
--expected-member-email | string | no | the member's email, checked before anything changes |
--request-key | string | yes | a key that makes repeating the same write safe |
--wait | boolean | no | after you approve it, follow it through until it is applied, failed or needs action |
--timeout-seconds | integer | no | how long to follow it (default: until the approval lapses) |
Every command also takes the global flags.
Returns
The data of the result that --json prints:
--json: { status: 'awaiting_approval', approvalId, approvalUrl, paymentIds: [], expiresAt, requestKey, next: { argv } }; a person, or --wait: { approval, requestKey }, with --wait also command: PermissionCommandView (status applied, failed or actionable)Errors
Generated from capxul schema org permission assign.