> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hexclave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Revoke a global permission from a user

> Revoke a global permission from a user



## OpenAPI

````yaml /openapi/server.json delete /project-permissions/{user_id}/{permission_id}
openapi: 3.1.0
info:
  title: Hexclave REST API
  version: 1.0.0
  description: >-
    The Hexclave REST API. All request headers are documented as canonical
    `X-Hexclave-*`; the equivalent `X-Stack-*` aliases are accepted on every
    endpoint for backwards compatibility. Response headers
    `X-Hexclave-actual-status`, `X-Hexclave-known-error`, and
    `X-Hexclave-request-id` are emitted alongside their legacy `X-Stack-*`
    equivalents.
servers:
  - url: https://api.hexclave.com/api/v1
    description: Hexclave REST API
security: []
paths:
  /project-permissions/{user_id}/{permission_id}:
    delete:
      tags:
        - Permissions
      summary: Revoke a global permission from a user
      description: Revoke a global permission from a user
      parameters:
        - name: user_id
          in: path
          schema:
            type: string
            example: 3241a285-8329-4d69-8f3d-316e08cf140c
            description: >-
              The ID of the user, or the special value `me` for the currently
              authenticated user
          description: >-
            The ID of the user, or the special value `me` for the currently
            authenticated user
          required: true
        - name: permission_id
          in: path
          schema:
            type: string
            example: read_secret_info
            description: >-
              The permission ID used to uniquely identify a permission. Can
              either be a custom permission with lowercase letters, numbers,
              `:`, and `_` characters, or one of the system permissions:
              `$update_team`, `$delete_team`, `$read_members`,
              `$remove_members`, `$invite_members`, `$manage_api_keys`
          description: >-
            The permission ID used to uniquely identify a permission. Can either
            be a custom permission with lowercase letters, numbers, `:`, and `_`
            characters, or one of the system permissions: `$update_team`,
            `$delete_team`, `$read_members`, `$remove_members`,
            `$invite_members`, `$manage_api_keys`
          required: true
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Always equal to true.
                    example: true
                required:
                  - success

````