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

# People and permissions

> Invite teammates to your workspace and control what they can see and do.

Aspect uses two levels of access: a **workspace role** that sets someone's overall standing in your workspace, and **project roles** that control what they can do inside individual projects.

For people outside your team (clients, reviewers, freelancers who just need to see a deliverable), you usually don't need to invite them at all. [Share links](/guides/sharing) let them view content without an account.

## Invite someone to your workspace

<Steps>
  <Step title="Open workspace settings">
    In [app.aspect.inc](https://app.aspect.inc), open your workspace settings and go to the People page.
  </Step>

  <Step title="Add the person">
    Enter their email address and choose their workspace role.
  </Step>

  <Step title="Adjust project access">
    If needed, give them specific roles on individual projects. Members get default access to every project automatically; Limited Members only see projects you explicitly grant.
  </Step>
</Steps>

## Workspace roles

| Role           | What it means                                                                                                                  |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Owner          | Full admin access to the workspace and all projects. Owners manage people, settings, and can delete projects.                  |
| Member         | Can access all projects in the workspace at each project's default role, and can create new projects.                          |
| Limited Member | Can only access projects they have been explicitly given permission on. Everything else in the workspace is invisible to them. |

Use Limited Member for people who should only ever see specific projects - for example, an outside editor working on one campaign.

## Project roles

Within a project, each person has a role that controls what they can do with everything inside it:

| Role        | Can do                                   |
| ----------- | ---------------------------------------- |
| Full Access | View, download, comment, edit, and share |
| Editor      | View, download, comment, and edit        |
| Commenter   | View, download, and comment              |
| Downloader  | View and download                        |
| Viewer      | View only                                |

Each project also has a **default role** - this is the access level workspace Members get automatically. You can override it per person: give someone a higher role on a project they lead, or set a Member to No Access on a project they shouldn't see.

## Access flows down

Permissions are set at the project level and flow down to everything inside. If someone is an Editor on a project, they are an Editor on every folder, asset, and collection in that project - you don't need to grant access item by item.

This keeps permissions simple to reason about: to know what someone can do with a file, look at their role on the project the file lives in.

## Manage people on a project

Each project has its own People page in the project settings. From there you can:

* See everyone who has access to the project and their role
* Add a person to the project with a specific role
* Change someone's role
* Remove someone's access to the project

<Note>
  Workspace Owners always have full access to every project. Their access can't be reduced through project roles.
</Note>

## Related guides

<CardGroup cols={2}>
  <Card title="Sharing" href="/guides/sharing">
    Give outside people access with a link instead of an invite.
  </Card>

  <Card title="Core concepts" href="/concepts/core-concepts">
    How workspaces, projects, and assets fit together.
  </Card>
</CardGroup>