Error codes

ROLE_PERMISSION_DENIED

You are not allowed to do this, so nothing was signed.

Exit code: 4 · Who acts: You or another person, after you read the current state, or by waiting · From: the CLI, the SDK and the backend

What it means

You are not allowed to do this, so nothing was signed.

Common causes

  • You are not a member, an Owner or a department holder of the Organization.
  • The amount is over your limit, or the recipient is not allowed.

Fix it

  1. Read reason in the error. The reasons are listed below.
  2. See your role and limits: capxul org me.
  3. Ask an Owner to give you the permission, or to do it for you.

Reasons

details.reason says why:

ReasonMeaning
over_capThe amount is more than one payment you may send.
daily_capThe amount would take you over what you may send today.
not_memberYou are not a member of the Organization.
not_ownerOnly an Owner of the Organization's account can do this.
not_holderYou hold no role for this department.
disallowed_recipientYou may not pay this recipient.
condition_violationThe call breaks a condition of your permission.
budget_exhaustedYour spending budget for this period is used up.
manage_books_requiredChanging the books needs the Manage books permission.

In JSON and the SDK

With --json, the CLI prints:

{
  "outcome": "refused",
  "error": {
    "code": "ROLE_PERMISSION_DENIED",
    "message": "…"
  }
}

In the SDK, a failed result has result.error.code === "ROLE_PERMISSION_DENIED". Branch on the code, not on the message: the message is written for people and can change.

Commands that can answer with it

On this page