# Manage Team Members and Permissions
This article covers team members added to your project via the **Invite User** button in the **Edit Team** page. If you are looking for more information about Users in the Backoffice, see the [Users](https://docs.umbraco.com/umbraco-cms/fundamentals/data/users) article. Users added through the backoffice do not have access to the Umbraco Cloud Portal.
Team members are automatically added as users in the Backoffice of all environments for the project. These users can clone the project locally and log in using the same credentials they use for Umbraco Cloud.
When adding a user, the default permission is *Read* for each environment. You can assign backoffice user groups to the user for each environment.
## Team Member User Permissions
User Permissions for each environment can be set in the **Edit Team** page from the **Overview** dropdown. User Permissions can be set per environment. For example, a user can have Write access on the left-most mainline environment and Read access on the Live environment.
Team Member User Permission
* **Admin**: Has access to everything on a project. An admin can delete a project and edit the team. An admin can deploy changes between environments in the Project Portal and has access to git, as well as the Power Tools Kudu.
* **Read**: A team member with Read permissions can only view the project in the portal as well as the backoffice. They are unable to deploy or make changes to the project itself. They can clone down the project, but cannot push changes they have made locally. By default, they are added as an admin in the backoffice so they can make changes in the backoffice. If you want to change this, see Team Member Permissions in the Umbraco Backoffice below.
* **Write**: A team member with Write permissions can do everything on a project except delete it and edit the team. A user with Write permissions can deploy changes between environments through the portal. They have access to the git repositories and can push local changes to the environment.
* **No Access**: A team member with no access permissions cannot restart the environment, deploy changes between environments, check error logs or log files, or access Kudo in the Project Portal. They can view the project in the portal and access the backoffice.
## Backoffice User Groups for Team Members
You can view the user group memberships of the project’s backoffice users. Currently, you can manage the backoffice user groups of a user through the Umbraco backoffice. A backoffice user is only created once the user logs into the backoffice of the project for the first time.
## Team Members Pending Invitation
Find invitation details in the **Member(s) who still need to accept the project invitation** section of the **Edit Team** page. You have the following options:
* View the team member's name and email.
* See the expiration date of the invitation.
* Check the status of the invitation.
* Copy the invitation link.
* Resend the invitation.
* Delete the invitation.
## [Technical Contacts](https://docs.umbraco.com/umbraco-cloud/begin-your-cloud-journey/project-features/team-members/technical-contact)
To ensure information about server maintenance reaches the correct person, add/update the technical contact to your Umbraco Cloud project.
---
# Agent Instructions: 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.umbraco.com/umbraco-cloud/begin-your-cloud-journey/project-features/team-members.md?ask=
```
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.
