A valid request URL is required to generate request examples{
"permissions": [
"organization:update"
]
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}List the permission catalogue
Requires roles:read. The catalogue lives in Go, not in the database: the set of things the system can do is a fact of the codebase, while who holds what is data.
A valid request URL is required to generate request examples{
"permissions": [
"organization:update"
]
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}Autorizações
A staff session token, uk_st_…. Minted by sign-up, sign-in or the two-factor exchange. Only a 401 means it is spent; not_a_member (403) is about the organization named in X-Organization-Id and leaves the token good for the others.
Cabeçalhos
The organization the caller is acting on — the org_… code that appears in the panel URL. It identifies; the membership JOIN is what authorizes, so a forged code reads nothing: the answer is not_a_member (403), which does not mean the session is over. Absent, the session's default organization answers, or — if that membership was revoked while the session was open — any other one the caller still holds.
Resposta
Every permission the role editor may offer.
A fine-grained capability. The catalogue lives in Go; which role holds which lives in the database.
organization:update, organization:delete, members:read, members:write, roles:read, roles:manage, api_keys:read, api_keys:write, customers:read, customers:write