> 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-update-workspace-user.md).

# Action: Update Workspace User

<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 Update Workspace User action modifies a user’s permissions or role within a specific DocuSign workspace.</p>

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

#### Example User Story

I want to update a colleague’s permissions in our DocuSign workspace, so they can help manage and edit project documents as needed.

#### Fields

| Field Name | Field Type | Required |
| ---------- | ---------- | -------- |
| accountId  | String     | Yes      |
| userId     | String     | Yes      |
| userData   | Object     | Yes      |

### Related Connections

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

### Related Automations

Example link

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

```
{
  "handle": "update-workspace-user",
  "state": "inDev",
  "meta": {
    "short": "Update Workspace User",
    "description": "Updates an existing user in a Docusign workspace."
  },
  "input": [
    {
      "name": "accountId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The Docusign account ID."
      }
    },
    {
      "name": "userId",
      "type": "String",
      "required": true,
      "meta": {
        "description": "The ID of the user to update."
      }
    },
    {
      "name": "userData",
      "type": "Object",
      "required": true,
      "meta": {
        "description": "The updated user data."
      }
    }
  ],
  "output": [
    {
      "name": "updatedUser",
      "type": "Object",
      "selector": ["user"],
      "meta": {
        "description": "The updated user details."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "PUT",
        "path": "/v2.1/accounts/{{accountId}}/users/{{userId}}",
        "headers": {
          "Content-Type": "application/json"
        },
        "bodyTemplate": {
          "value": "{{userData}}",
          "placeholders": [
            {
              "name": "userData",
              "type": "Object",
              "description": "The updated user data.",
              "required": true
            }
          ]
        }
      }
    }
  ]
}

```

<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-update-workspace-user.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.