role_forbidden: The member's roles do not allow this
An organisation member acts only on routes its roles allow, and only on budgets, streams, approvals, policies and cases of its organisation or team: a viewer reads; an approver reads and decides approvals; a funder reads and funds (opens budgets for its team, opens streams, meters, checkpoints, reserves, opens tasks and recourse cases); an admin reads, decides approvals, controls (freeze, thaw, stop, amend, revoke, close, resolve and escalate recourse) and governs (policies and bindings, teams, members, budget assignment, roles). An admin does not fund. The same answer covers an object outside the member's scope and one that does not exist. Nothing happened.
What to do
- This member's roles (funder, admin, approver, viewer at an organisation or team) do not allow this action on this object; ask an admin of its organisation, or use the owner token.
On the wire
HTTP 403, {"error": "forbidden", "reason": "role_forbidden"} with errorDetail.
See organisations and roles and all error codes.