> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Revoke a Role from Users in Batch > Takes a role away from several people at once, naming them in the body. It is a POST rather than a DELETE because the people travel in a request body; `DELETE /v1/roles/{id}/users/{userId}` does the same for exactly one. Only the DIRECT grant is revoked. Somebody who also holds this role through a group keeps it, and the call still answers 204 — if the intent is to remove their access entirely, take them out of the group too. Revoking from somebody who does not hold the role is not an error. On success the response has no body (204). Failures: - `400` — `users` is missing or empty. - `404` — no such role in your organization. - `503 IDE-0066` — the identity provider is unavailable (unreachable, too slow to answer, or failing). Nothing about the request was wrong; retry it later. ## OpenAPI ````yaml /en/openapi/v3-current/AM-identity.yaml post /v1/roles/{id}/users/remove openapi: 3.1.0 info: contact: name: Lerian Studio url: https://lerian.studio description: OpenAPI 3.1 surface for the Access Manager identity component. license: name: Lerian Studio General License title: Plugin Access Manager — Identity API version: v1 servers: - url: https://identity.sandbox.lerian.net security: [] tags: - description: >- M2M-only: each plugin declares its own permissions, roles and M2M contract, and the server reconciles them. name: Declarations - description: >- A tenant administrator's customers. Each partner holds what its credentials may DO (permissions, per product) and WHERE they may do it (scope, per product and dimension); an M2M application attached to one is confined to that intersection. Administrator-only: authorized on the "partners" resource, and every route resolves the owning organization from the caller's token. name: Partners paths: /v1/roles/{id}/users/remove: post: tags: - Roles summary: Revoke a Role from Users in Batch description: >- Takes a role away from several people at once, naming them in the body. It is a POST rather than a DELETE because the people travel in a request body; `DELETE /v1/roles/{id}/users/{userId}` does the same for exactly one. Only the DIRECT grant is revoked. Somebody who also holds this role through a group keeps it, and the call still answers 204 — if the intent is to remove their access entirely, take them out of the group too. Revoking from somebody who does not hold the role is not an error. On success the response has no body (204). Failures: - `400` — `users` is missing or empty. - `404` — no such role in your organization. - `503 IDE-0066` — the identity provider is unavailable (unreachable, too slow to answer, or failing). Nothing about the request was wrong; retry it later. operationId: revokeRoleFromUsersBatch parameters: - description: Role ID. in: path name: id required: true schema: description: Role ID. examples: - midaz-editor type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/AssignUsersInput' description: The users to revoke the role from. required: true responses: '204': description: No Content '400': content: application/json: schema: $ref: '#/components/schemas/HTTPError' description: Bad Request '404': content: application/json: schema: $ref: '#/components/schemas/HTTPError' description: Not Found '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity '500': content: application/json: schema: $ref: '#/components/schemas/HTTPError' description: Internal Server Error '503': content: application/json: schema: $ref: '#/components/schemas/HTTPError' description: Service Unavailable security: - BearerAuth: [] components: schemas: AssignUsersInput: additionalProperties: false properties: users: description: User identifiers. items: type: string minItems: 1 type: array required: - users type: object HTTPError: additionalProperties: false properties: code: type: string entityType: type: string err: {} message: type: string title: type: string type: object Detail: additionalProperties: true properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object Upstream: additionalProperties: false properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.