> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/human-connections/docusign/docusign/action-revoke-workspace-user-access.md).

# Action: Revoke Workspace User Access

<p align="center"><a class="button primary" data-icon="circle-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscriptions</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>

<figure><img src="/files/NqT6jFUNiB68dGrhBI5F" alt=""><figcaption></figcaption></figure>

<p align="center">The Cancel Maestro Workflow Instance action stops an in-progress Maestro workflow, halting any further processing or notifications.</p>

{% embed url="<https://www.youtube.com/watch?v=CyuUuaBSZzA>" %}

#### Example User Story

I want to revoke access for former team members from our DocuSign workspaces, so only current employees can view or edit sensitive documents.

#### Fields

| Field Name  | Field Type | Required |
| ----------- | ---------- | -------- |
| workspaceId | String     | Yes      |
| userId      | String     | Yes      |
| accessToken | String     | Yes      |

### Related Connections

[Docusign](/human-connections/docusign/docusign.md)

### Related Automations

Example link

### Code (Apache v2.0): Operation

```
{
  "handle": "revoke-workspace-user-access",
  "state": "inDev",
  "meta": {
    "short": "Revoke Workspace User Access",
    "description": "Revokes a user's access to a specific workspace in DocuSign."
  },
  "input": [
    {
      "name": "workspaceId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the workspace from which to revoke user access."
      }
    },
    {
      "name": "userId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the user whose access is to be revoked."
      }
    }
  ],
  "output": [
    {
      "name": "success",
      "type": "Boolean",
      "selector": ["success"],
      "meta": {
        "description": "Indicates whether the operation was successful."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "DELETE",
        "path": "/v2.1/workspaces/{{workspaceId}}/users/{{userId}}",
        "headers": {
          "Content-Type": "application/json"
        }
      }
    }
  ]
}

```

<p align="center"><a class="button primary" data-icon="square-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscription</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.planetcrust.com/human-connections/docusign/docusign/action-revoke-workspace-user-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.