> For the complete documentation index, see [llms.txt](https://docs.pay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pay.io/account-settings/team-management-roles-and-permissions/invite-or-remove-team-members.md).

# Invite or Remove Team Members

**Administrators** can invite new team members directly from the Merchant Console, assigning them a role from the moment they join.&#x20;

Access can also be revoked at any time to ensure former employees or external collaborators can no longer act on behalf of your organisation.

<div data-with-frame="true"><figure><img src="/files/UqCfpk7wrLwIEdCCbbmV" alt=""><figcaption></figcaption></figure></div>

### Inviting a Team Member

{% stepper %}
{% step %}

#### **Navigate to the Team Tab**

From the left-hand navigation, go to **Manage Console → Settings**. Under **Organisational Settings**, select the **Team** tab.
{% endstep %}

{% step %}

#### **Click "Invite Someone"**

Click the **"+ Invite someone"** button in the top right-hand corner of the Team Member's table. A modal window will appear.

<div data-with-frame="true"><figure><img src="/files/b1Du0wmlfMrHcNXGmC87" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### **Enter the Team Member's Details**

Complete the following fields in the **Invite Team Member** modal:

* **First name** → the invitee's first name.
* **Last name**→ the invitee's last name.
* **Email address** → the email address to which the invitation will be sent.
* **Assign role** → select the role the team member will hold upon joining. Choose from **Administrator**, **Manager**, or **Viewer**.

{% hint style="info" %}
Not sure which role to assign? Refer to the [Roles and Permissions](https://docs.pay.io/settings/team/roles-and-permissions) guide for a full breakdown of what each role can access. You can also view the matrix at any time by clicking **"Roles and permissions"** on the Team tab.
{% endhint %}
{% endstep %}

{% step %}

#### **Send the Invitation**

Click the **"Invite team member"** button. The invitee will receive a secure activation link at the email address provided. Once they complete the sign-up flow, they will be linked to your merchant account with the role you assigned.

{% hint style="warning" %}
The assigned role and merchant account context are enforced from the moment the invitee activates their account. Ensure you select the correct role before sending — you can always update it afterwards from the Team tab.&#x20;
{% endhint %}
{% endstep %}
{% endstepper %}

***

### Removing a Team Member

When a team member leaves your organisation or no longer requires access, their account should be removed promptly to maintain the security and integrity of your console.

{% stepper %}
{% step %}

#### **Locate the Team Member**

From the **Team** tab, find the team member you wish to remove in the table.
{% endstep %}

{% step %}

#### **Click the Remove Icon**

Click the **delete icon** in the **Actions** column of their row. A confirmation modal will appear.

<div data-with-frame="true"><figure><img src="/files/MBbvcNjTvwgaoGQ9NfhK" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### **Confirm Removal**

Review the confirmation prompt and confirm the removal. The team member's access will be revoked immediately — they will no longer be able to log in to the Merchant Console or perform any actions on behalf of your organisation.

{% hint style="warning" %}
Removal is a permanent action and cannot be undone. However, all historical activity and audit logs associated with the removed user are retained for compliance purposes.

Only **Administrator** users can remove team members. If you need a user removed and do not have Administrator access, contact your organisation's Administrator.
{% endhint %}
{% endstep %}
{% endstepper %}

***

#### Things to Bear in Mind

* A team member's role can be updated at any time after they have joined. Role changes take effect immediately.
* Removing a user revokes their access instantly but preserves all historical records of their activity, your audit trail remains intact.
* A user can be invited again if they have been removed from the team members.
* If you are the **account Owner**, your account cannot be removed by other Administrators.
* Always review your team's roles periodically to ensure the principle of least privilege is maintained as your organisation scales.

***

#### What's Next?

* [Team Management (Roles and Permissions)](/account-settings/team-management-roles-and-permissions.md) to understand what each role can access across the Merchant Console.
* [Account Settings Overview](/account-settings/settings-overview.md) to explore all available settings for your account and organisation.
* [API Keys and Webhooks](/account-settings/managing-api-keys.md) to manage API credentials and event subscriptions for your integration.


---

# 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.pay.io/account-settings/team-management-roles-and-permissions/invite-or-remove-team-members.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.
