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

> ## Agent Instructions
> These are the docs for Sevalla, a platform for deploying applications, databases, static sites, object storage and load balancers. The dashboard is at https://app.sevalla.com.
> Bold text in steps is an exact dashboard label.
> To act on a Sevalla account, prefer the Sevalla MCP server (https://mcp.sevalla.com/mcp, see https://docs.sevalla.com/ai-agents/overview.md), then the Sevalla CLI (https://docs.sevalla.com/developer-tools/cli.md), then the REST API (https://api-docs.sevalla.com, OpenAPI spec at https://api.sevalla.com/v3/openapi.json).
> Every page index is at https://docs.sevalla.com/llms.txt.

# Project access

> Invite people to a project as project admins or developers, or as administrators of some of its services, then update their access, remove them or cancel invitations.

Project access lets people work on one project's services without access to the rest of the company. You manage it on the project's **Access management** tab, which lists everyone who can reach the project and every pending invitation.

## Project roles

You can give someone one of two kinds of access from a project:

| Access level | Role | What the person can do |
| - | - | - |
| **Project** | **Project developer** (the default) | See the project and its usage, see who has access, and create, update and delete any service in the project. |
| **Project** | **Project admin** | Everything a project developer can do, plus invite people to the project and update or remove their access. |
| **Service** | Administrator of each service you pick (**App administrator**, **Database administrator**, **Static site administrator**, **Object storage administrator** or **Load balancer administrator**) | View and update only the selected services, but not delete them. They don't see the rest of the project. |

Project roles don't include renaming or deleting the project, adding existing services to it, or removing services from it: those stay with company owners, admins and developers. Only company owners and admins can manage the project's usage alert. [Projects](/projects/overview#how-projects-work) has the full table.

Within a company, each person has one kind of access: company-wide, project or service. Giving someone project access replaces any service access they had in that company, and the reverse. Company-wide access (owner, admin, developer, billing) is managed in **User management**, not here: see [Users and roles](/company/users-and-roles).

<Info>
  Company owners, admins and developers, and project admins, can invite people and change their access. Project developers can see the list but not change it.
</Info>

## See who has access

Open the project, then click the **Access management** tab. The list shows pending invitations first, then people, with these columns:

| Column | What it shows |
| - | - |
| **Name** | The person's name, or the invited email address with a **Pending** badge. **You** marks your own row. |
| **Email** | Their email address. |
| **2FA** | Their two-factor method: **App**, **Email** or **None**, or **n/a** for an invitation. |
| **Role** | A company role (for example **Company admin**), **Project admin** or **Project developer**, or **Service-level access**. Point at **Service-level access** to see which services and roles it covers. |

Type in **Filter by name or email…** to find someone. You can't change your own row. People with company-wide access have a link to **User management** instead of actions.

## Invite people to a project

<Steps>
  <Step title="Open the invite sheet">
    On the project's **Access management** tab, click **Invite users**.
  </Step>

  <Step title="Enter the email addresses">
    In **Email addresses**, enter up to 10 addresses, separated by commas.
  </Step>

  <Step title="Choose the access level">
    Under **Access level**, choose **Project** to give access to the whole project, then pick the role: **Project developer** or **Project admin**. Or choose **Service**, then pick the services each person administers.
  </Step>

  <Step title="Send the invitations">
    Click **Send invitation** (or **Send 3 invitations**, and so on).
  </Step>
</Steps>

What happens next depends on the address:

* **The address belongs to a Sevalla account**: Sevalla gives the person the access right away and emails them that they were added to the project.
* **The address has no Sevalla account**: Sevalla emails an invitation with a link to sign up and join. Until they join, the invitation shows at the top of the list with a **Pending** badge. Invitation links don't expire; cancel an invitation to stop its link working.

Project admins can't invite people who have company-wide access, or service access outside this project. Ask a company owner or admin instead.

## Update access

<Steps>
  <Step title="Open the update sheet">
    On the project's **Access management** tab, click the actions menu (**...**) on the person's row, then click **Update access**.
  </Step>

  <Step title="Change the access">
    Under **Access level**, change the project role, or switch to **Service** and pick the services they administer.
  </Step>

  <Step title="Save">
    Click **Update access**.
  </Step>
</Steps>

The **Role** column shows the new access. If a project admin tries to change someone who also has access outside the project, the dashboard shows `Project admins cannot change this user`; ask a company owner or admin to make the change.

## Remove someone from a project

<Steps>
  <Step title="Choose the person">
    On the project's **Access management** tab, click the actions menu (**...**) on the person's row, then click **Remove from project**.
  </Step>

  <Step title="Confirm">
    Click **Remove**.
  </Step>
</Steps>

Sevalla removes their project role and their access to every service in the project, and they disappear from the list. Access they have to other projects stays.

## Copy or cancel an invitation

To send an invitation link yourself, click the actions menu (**...**) on the invitation's row, then click **Copy invitation link**.

To cancel an invitation:

<Steps>
  <Step title="Choose the invitation">
    Click the actions menu (**...**) on the invitation's row, then click **Cancel invitation**.
  </Step>

  <Step title="Confirm">
    Click **Cancel invitation** in the dialog.
  </Step>
</Steps>

The invitation leaves the list and its link stops working. You can't undo this; send a new invitation instead.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.