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

# Remove somebody from your account

> Removes every grant by which they reach your organisations and disables their sign-in. The sign-in account is kept, disabled, so the audit history stays joinable and re-inviting them later does not create a second identity. Takes effect at once: an access token they already hold keeps decoding for up to an hour, and every request made with it is refused.

**Only the account owner may remove somebody** — 403 `not_customer_owner` for everyone else. Changing what a person reaches needs only ordinary access; removing the person is the owner's act. The owner cannot remove themselves (409 `cannot_delete_owner`): transfer ownership first, and the new owner removes them.

A guest — somebody who belongs to another account and reaches organisations here by invitation — answers 404, because their account is not yours to remove. Take back the access you granted through `/users/{principalId}/organisations` instead.



## OpenAPI

````yaml /api-reference/specs/administration.json delete /users/{principalId}
openapi: 3.0.1
info:
  title: Administration API
  description: >-
    Manage your Flow Payroll account: the organisations it owns, the people who
    can sign in to it, the API tokens it holds, its brand, and a feed of recent
    administration activity. Every resource is scoped to the account your
    credentials belong to, so no request ever names a customer and the
    `X-Org-Id` header is not used.
  version: v1
servers:
  - url: https://api.sandbox.flowpayroll.ai/v1/administration
security:
  - X-Auth-Token: []
tags:
  - name: Customer
    description: >-
      Your account: the customer every other resource on this API belongs to.
      Read it and rename it.
  - name: Organisations
    description: >-
      The organisations your account owns: list them with headcounts and your
      access to each, get one in full, and add one or several at a time.
  - name: Users
    description: >-
      The people who can sign in to your account: list, invite (one or many),
      resend invitations, and manage each person's direct grants and
      account-wide access.
  - name: API tokens
    description: >-
      The client credentials your integrations authenticate with: create (the
      secret is shown once), rename, rotate, revoke, and manage which
      organisations each token reaches.
  - name: Activity
    description: Recent administration actions in your account, newest first.
paths:
  /users/{principalId}:
    delete:
      tags:
        - Users
      summary: Remove somebody from your account
      description: >-
        Removes every grant by which they reach your organisations and disables
        their sign-in. The sign-in account is kept, disabled, so the audit
        history stays joinable and re-inviting them later does not create a
        second identity. Takes effect at once: an access token they already hold
        keeps decoding for up to an hour, and every request made with it is
        refused.


        **Only the account owner may remove somebody** — 403
        `not_customer_owner` for everyone else. Changing what a person reaches
        needs only ordinary access; removing the person is the owner's act. The
        owner cannot remove themselves (409 `cannot_delete_owner`): transfer
        ownership first, and the new owner removes them.


        A guest — somebody who belongs to another account and reaches
        organisations here by invitation — answers 404, because their account is
        not yours to remove. Take back the access you granted through
        `/users/{principalId}/organisations` instead.
      operationId: RevokeUser
      parameters:
        - name: principalId
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserRevokedResponseResponseBody'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ObjectResponseBody'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ObjectResponseBody'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ObjectResponseBody'
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ObjectResponseBody'
components:
  schemas:
    UserRevokedResponseResponseBody:
      type: object
      properties:
        message:
          $ref: '#/components/schemas/MessageWithTokenResponse'
        content:
          $ref: '#/components/schemas/UserRevokedResponseContentResponse'
        validationIssues:
          type: array
          items:
            $ref: '#/components/schemas/ValidationIssue'
          nullable: true
      additionalProperties: false
    ObjectResponseBody:
      type: object
      properties:
        message:
          $ref: '#/components/schemas/MessageWithTokenResponse'
        content:
          $ref: '#/components/schemas/ObjectContentResponse'
        validationIssues:
          type: array
          items:
            $ref: '#/components/schemas/ValidationIssue'
          nullable: true
      additionalProperties: false
    MessageWithTokenResponse:
      type: object
      properties:
        text:
          type: string
        token:
          type: string
        tokenArguments:
          type: array
          items:
            $ref: '#/components/schemas/ValidationIssueArgument'
          nullable: true
      additionalProperties: false
    UserRevokedResponseContentResponse:
      type: object
      properties:
        data:
          $ref: '#/components/schemas/UserRevokedResponse'
        metadata:
          $ref: '#/components/schemas/ContentMetadataResponse'
      additionalProperties: false
    ValidationIssue:
      type: object
      properties:
        field:
          type: string
        reason:
          type: string
        reasonToken:
          type: string
        reasonTokenArguments:
          type: array
          items:
            $ref: '#/components/schemas/ValidationIssueArgument'
          nullable: true
      additionalProperties: false
    ObjectContentResponse:
      type: object
      properties:
        data:
          nullable: true
        metadata:
          $ref: '#/components/schemas/ContentMetadataResponse'
      additionalProperties: false
    ValidationIssueArgument:
      type: object
      properties:
        name:
          type: string
        value:
          nullable: true
      additionalProperties: false
    UserRevokedResponse:
      type: object
      properties:
        principalId:
          type: string
          description: The person removed.
      additionalProperties: false
      description: Confirmation that somebody was removed from the account.
    ContentMetadataResponse:
      type: object
      properties:
        dateFormat:
          type: string
        dateTimeFormat:
          type: string
        paginationToken:
          type: string
          nullable: true
      additionalProperties: false
  securitySchemes:
    X-Auth-Token:
      type: apiKey
      description: FlowPayroll JWT (raw token, no Bearer prefix)
      name: X-Auth-Token
      in: header

````

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