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

# Team Management

In Notch, team members are crucial in collaborating and managing spaces. Team members can have either an Admin or Member role, each with distinct permissions and capabilities. Admins oversee account and team settings, while Members focus on creating and managing spaces and lists. 

In the Team Members section, you can view all current team members, assign roles (Admin or Member), and invite new team members. Admins can update account details, while Members can create and manage spaces and lists and invite new team members.

<figure><img src="/files/rMFvuKj4o27XslxnbEuc" alt=""><figcaption><p>Team Member Settings</p></figcaption></figure>

### Accessing Team Member Settings

1. Click on your profile icon at the top left in the navigation bar.
2. From the dropdown menu, select "Team Settings".
3. In the Team Settings, select "Team Members" to view and manage your team.

{% hint style="warning" %}
Only admin user can access team settings
{% endhint %}

### Roles and Permissions

#### Admin Role

Admins have full access to team settings and can update account details. Their permissions include:

* Accessing and modifying team settings
* Updating account details
* Managing Integrations
* [Setting up custom domains](/account-management/team-settings/custom-domain.md)
* [Customizing space branding](/account-management/team-settings/branding.md)
* Managing team member roles and permissions.
* [Manage  subscription ](/account-management/team-settings/pricing-and-billing.md)

#### Member Role

Members have more focused capabilities centered around creating and managing spaces. Their responsibilities include:

* Creating and editing spaces.
* [Sharing spaces](broken://pages/wMH4LPIxFYc22JpTeaPS) with clients.
* [Creating & managing space lists](/more-features/space-lists.md).
* Inviting new team members to join the team.

### Inviting New Team Members

{% hint style="success" %}
Both Admins and Members can invite new team members.&#x20;
{% endhint %}

You can begin the invitation process from one of the following locations:

* **Navigation Bar**: Click on "Invite Team Member" in the bottom left corner.
* **Profile Icon**: Click on your profile icon at the top left in the navigation bar and select "Invite Team Member" from the dropdown menu.
* **Team Settings (Admin Only)**: Admin users can also invite new team members from the "Team Members" section within "Team Settings".

Inviting new team members:

1. Once you've accessed the invitation screen, provide the email address of the new member you want to invite.
2. Click the "Send Invitation" button to invite the new team member.
3. Your new team member will receive an invitation to your team account.

<figure><img src="/files/SPg21fW4e3hOYkibXqOU" alt=""><figcaption><p>Invite new team members by sending an invite to their email address</p></figcaption></figure>


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.notch.so/account-management/team-settings/team-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.