> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/project-management/workspaces/reference-workspaces/motion-teams-setting-workspace-permissions.md).

# Motion Teams: Setting Workspace Permissions

For Motion teams, projects and tasks within a workspace are only visible to those who have been successfully added to that workspace by the team admin.

**Steps for adding teammates to a workspace:**

1. Click the settings icon in the upper left-hand corner of the Motion app.
2. Scroll down and select the specific workspace you would like to add your teammate.
3. In the '**overview**' section of your workspace settings you will see a list of member already added to the workspace.
4. Select '***+ Add Member***' beneath the list of active workspace members.
5. This will populate a list of selectable team members.
6. Select the team member you wish to add to the workspace.
7. Your new team member will now have access to this workspaces tasks and projects.


---

# 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://www.usemotion.com/help/project-management/workspaces/reference-workspaces/motion-teams-setting-workspace-permissions.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.