> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/settings/member-management.md).

# Members

Invite people, change their roles, remove them and transfer ownership.

Admins manage people from the workspace name at the top left: **Members**.

{% embed url="<https://app.screendesk.io/recordings/440f1ab3-dc54-4805-84c3-b54eee1b0c35>" %}

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2F9yHHYvznvXA7CkZoleL8%2Fdocs-panel-members.png?alt=media" alt="Settings, Members"><figcaption></figcaption></figure>

### Invite people

Click **Invite member**, add each person's email with a role, then **Send invitations**. They get an email with a link to join.

Invitations wait on the **Pending invitations** tab, where you can **Resend** or **Revoke** them.

Not sure which role? See [User roles and permissions](https://docs.screendesk.io/settings/member-management/user-roles-and-permissions.md).

### Change a role or remove someone

On the **Members** tab, edit a member to change their role, or click **Remove**. A removed member loses access straight away.

### Transfer ownership

The owner can hand the workspace to another member under **Transfer ownership**, at the bottom of the page. The new owner becomes an admin if they weren't one. Your own role doesn't change.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/settings/member-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
