POST /api/v1/admin/orgs/:slug/role-overrides
This page is auto-generated from
src/admin/routes.ts. Do not edit by hand — seedocs/dev/docs-auto-sync.md.
:warning: Heuristic extraction — not a contract. Response shapes below are mined from
c.json(...)literals in the handler via an AST walker. Computed fields, ternaries, and non-literal returns are shown as placeholders. Refer to the linked source file for the authoritative behaviour.
POST /api/v1/admin/orgs/:slug/role-overrides
Section titled “POST /api/v1/admin/orgs/:slug/role-overrides”Authentication
Section titled “Authentication”Requires the following capability(ies):
members:w
Middleware
Section titled “Middleware”Other middleware observed on this route (heuristic):
requireCapabilityadminBodyLimit
Responses
Section titled “Responses”HTTP 404
Section titled “HTTP 404”{ "error": "Org not found"}HTTP 400
Section titled “HTTP 400”{ "error": "Invalid JSON body"}HTTP 400
Section titled “HTTP 400”{ "error": "Body must be a JSON object"}HTTP 400
Section titled “HTTP 400”{ "error": "role must be one of: admin, member, viewer"}HTTP 400
Section titled “HTTP 400”{ "error": "owner role cannot be overridden"}HTTP 400
Section titled “HTTP 400”{ "error": "capability must be a known capability string"}HTTP 400
Section titled “HTTP 400”{ "error": "effect must be 'allow' or 'deny'"}HTTP 200
Section titled “HTTP 200”{ "role": <role>, "capability": <capability>, "effect": <effect>}Source
Section titled “Source”- File:
src/admin/routes.ts - Line: 396