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

# Remove someone from an organization

> Remove a user from an organization and from every virtual data plane, workspace and project
in it, which also withdraws a pending invite. The user's current sessions must reauthorize.
Their HoneyHive user stays, along with their memberships of other organizations. The
organization and the user are identified by the path parameters alone. The `x-hh-org-id`
header does not participate.

When an API key makes the request, it cannot remove a member who has signed in and whose
roles grant `org.roles.get`, `org.roles.set`, `org.fine_grained_api_key_cp.list` and
`org.fine_grained_api_key_cp.delete`, so someone in the organization can always revoke the
key. Such a request is refused with 409, and the member has to be removed in the HoneyHive
app. A member who has not signed in yet can be removed with an API key whatever their roles.
When the organization has no valid roles manifest in force, a member who has signed in
cannot be checked, and an API key's request to remove them is refused with 409.

Available on self-hosted deployments that do not enable an SSO group scheme. Elsewhere this
operation returns 404. An API key that carries a membership permission can carry no
permission other than the roles and membership permissions, and is created on an
organization.




## OpenAPI

````yaml https://raw.githubusercontent.com/honeyhiveai/honeyhive-openapi/main/control_plane_openapi.yaml delete /v1/orgs/{org_id}/members/{user_id}
openapi: 3.1.0
info:
  title: HoneyHive Control Plane API
  description: >
    Manage HoneyHive control-plane resources: organizations with their roles,
    templates and

    members, workspaces with their templates and members, projects with their
    members and

    alerts, and read org usage.


    Authentication requires a fine-grained control-plane API key (values

    start with `hh_fgcp_`), sent as `Authorization: Bearer <api-key>`.

    Project API keys used with the Data Plane API will not work here. Create

    a key in the HoneyHive app under an organization's or workspace's

    **Settings → API Keys**, or see

    [Authorization](https://docs.honeyhive.ai/v2/control-plane-sdk-reference/typescript#authorization)

    for details.
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
  version: 1.19.0
servers:
  - url: https://api.cp.us.honeyhive.ai
security: []
tags:
  - name: Alerts
    description: >
      Define and manage alerts. Alerts evaluate event metrics on a schedule and
      trigger notifications when configured thresholds are crossed.
  - name: Org Members
    description: >
      List an organization's members, invite people to it, set a member's roles,
      and remove people from it and from everything in it. Available on
      self-hosted deployments that do not enable an SSO group scheme.
  - name: Org Templates
    description: >
      Read and replace an organization's templates manifest, which defines the
      metrics and charts that new projects start with. Each workspace gets its
      own copy when it is created, so a new version reaches an existing
      workspace's projects only where that workspace's manifest merges with the
      organization's.
  - name: Orgs
    description: >
      Read an organization's display name and the email domains whose users join
      it automatically when they sign in, and update its display name.
  - name: Project Members
    description: >
      List a project's members, invite people to it, set a member's roles, and
      remove people from it. Available on self-hosted deployments that do not
      enable an SSO group scheme.
  - name: Projects
    description: >
      Create and manage projects within a workspace. A project is the container
      for the events, datasets, evaluations, and alerts logged against it.
  - name: Roles
    description: >
      Read and replace an organization's roles manifest, which defines its roles
      and the permissions each one grants. Available on self-hosted deployments
      only.
  - name: Usage
    description: >
      Read an organization's usage: events and computed metrics per calendar
      month, and current user, workspace and project counts.
  - name: Virtual Dataplanes
    description: >
      Create and manage virtual data planes. A virtual data plane is a logical
      tenant boundary inside an organization, hosted on a physical cluster;
      several virtual data planes commonly share one cluster. Workspaces live
      inside a virtual data plane.
  - name: Workspace Members
    description: >
      List a workspace's members, invite people to it, set a member's roles, and
      remove people from it and from every project in it. Available on
      self-hosted deployments that do not enable an SSO group scheme.
  - name: Workspace Templates
    description: >
      Read and replace a workspace's templates manifest, which defines the
      metrics and charts that new projects in the workspace start with.
  - name: Workspaces
    description: >
      Read and manage workspaces. A workspace groups the projects belonging to
      one team or environment, and owns the API keys and AI provider secrets its
      projects share.
paths:
  /v1/orgs/{org_id}/members/{user_id}:
    delete:
      tags:
        - Org Members
      summary: Remove someone from an organization
      description: >
        Remove a user from an organization and from every virtual data plane,
        workspace and project

        in it, which also withdraws a pending invite. The user's current
        sessions must reauthorize.

        Their HoneyHive user stays, along with their memberships of other
        organizations. The

        organization and the user are identified by the path parameters alone.
        The `x-hh-org-id`

        header does not participate.


        When an API key makes the request, it cannot remove a member who has
        signed in and whose

        roles grant `org.roles.get`, `org.roles.set`,
        `org.fine_grained_api_key_cp.list` and

        `org.fine_grained_api_key_cp.delete`, so someone in the organization can
        always revoke the

        key. Such a request is refused with 409, and the member has to be
        removed in the HoneyHive

        app. A member who has not signed in yet can be removed with an API key
        whatever their roles.

        When the organization has no valid roles manifest in force, a member who
        has signed in

        cannot be checked, and an API key's request to remove them is refused
        with 409.


        Available on self-hosted deployments that do not enable an SSO group
        scheme. Elsewhere this

        operation returns 404. An API key that carries a membership permission
        can carry no

        permission other than the roles and membership permissions, and is
        created on an

        organization.
      operationId: deleteOrgMember
      parameters:
        - in: path
          name: org_id
          required: true
          schema:
            type: string
          description: The unique identifier of the organization
        - in: path
          name: user_id
          required: true
          schema:
            type: string
          description: >-
            The member's user id, as the member list returns it. One person has
            the same user id in every organization, workspace and project
      responses:
        '200':
          description: User removed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteMemberResponse'
        '404':
          description: >-
            Organization not found, the user has no membership in it or in
            anything in it, the caller may not remove its members, or the
            deployment does not offer member management. The response does not
            say which.
        '409':
          description: >-
            The request came from an API key, and the member has signed in and
            can revoke API keys, or the organization has no valid roles manifest
            to check them against
      security:
        - ControlPlaneApiKey: []
components:
  schemas:
    DeleteMemberResponse:
      type: object
      properties:
        success:
          type: boolean
          enum:
            - true
      required:
        - success
      additionalProperties: false
  securitySchemes:
    ControlPlaneApiKey:
      type: http
      scheme: bearer
      description: >-
        A fine-grained control-plane API key (values begin with `hh_fgcp_`).
        Project API keys used with the Data Plane API will not work here. Create
        one in the HoneyHive app under an organization's or workspace's
        **Settings → API Keys**.

````

## Related topics

- [Org Members](https://docs.honeyhive.ai/v2/cli-reference/ref/org-members.md)
- [Org Members Methods](https://docs.honeyhive.ai/v2/control-plane-sdk-reference/typescript/ref/org-members/index.md)
- [Remove someone from a project](https://docs.honeyhive.ai/v2/control-plane-api-reference-autogen/project-members/remove-someone-from-a-project.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.