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

# Restore a Deactivated Member

> How to give a deactivated MCP Manager workspace member their access back: re-activate them in your identity provider when SCIM deactivated them, or invite them again when an administrator did. Covers what a deactivated member sees and exactly what each path restores.

A member is deactivated in one workspace in one of two ways: their identity provider (IdP) deprovisions them through [SCIM](https://docs.mcpmanager.ai/enterprise/scim.md), or an administrator deactivates them in MCP Manager. Either way, deactivation ends their membership in that workspace only. Their account stays active, so any other workspace they belong to is unaffected. Restore the membership the same way it was ended: in the IdP for an IdP deactivation, by invitation for an administrator's.

> [!NOTE]
>
> Inviting a member back needs the **Invite users** capability, which shows the **Add new users** button on People → Users. Deactivating a member needs **Remove users**. If you don't see the button, your role doesn't have the capability; any role can be granted it ([Capabilities](https://docs.mcpmanager.ai/deployment/rbac-and-roles/capabilities.md)).

## What a deactivated member sees

A deactivated member keeps their account, but every request they make to the workspace is refused:

* **AI clients and agents** get a JSON-RPC error with code `-32003` on every request to the workspace's gateways, delivered with HTTP 200 so MCP clients read it as a typed error. The message reads: "MCP Manager refused this request. Your access to this workspace has been deactivated by your identity provider or a workspace administrator. Ask your administrator to restore it. If you contact them, provide the correlation ID below."
* **The Admin API** answers HTTP 403 with the same sentence, and **the Admin MCP server** answers the same JSON-RPC error as the gateway.
* **The web app** refuses their requests in that workspace.

Deactivation revokes no token. A deactivated member's existing OAuth connections and personal access tokens stop working while the membership is inactive, and work again as soon as it is restored, so nobody has to reconnect their AI clients.

## How administrators can tell a member is deactivated

A deactivated member disappears from People → Users, from role and team member lists, and from user pickers, and their seat is released, so the workspace's licensed user count drops by one.

When a deactivated member's AI client keeps calling a gateway, MCP Manager raises an **Inactive member refused** alert: "A request from `<member>` was refused because their membership in this workspace is inactive. Their identity provider or an administrator deactivated it. Restore their membership to give them access again." The alert does not say which of the two deactivated them. If the member is SCIM-managed, assume the IdP did, because the **Deactivate user** button is disabled for SCIM-managed members.

## Restore a member your identity provider deactivated

A member that SCIM deprovisioned is restored by your IdP, which stays the source of truth for SCIM-managed people.

**1. Re-activate the person in your IdP**

Assign the person to the MCP Manager application again, or set them active, using whatever your IdP calls it (in Okta, reassign or reactivate the user; in Microsoft Entra ID, add the user back to the enterprise application's **Users and groups**).

**2. Let the IdP push the change**

The IdP sends MCP Manager a SCIM update with `active: true` (a `PATCH` or `PUT` to `/Users/{id}`), or creates the user again with `POST /Users`. Both restore the same profile and SCIM ID; a repeated `POST` for a deprovisioned member answers `201 Created` rather than a conflict. The change applies as soon as MCP Manager receives it, so how quickly that happens depends on your IdP's provisioning schedule.

**3. Check the member is back**

The person appears on [People → Users](https://app.mcpmanager.ai/settings/people/users) again, and their AI clients work with their existing tokens.

Re-activating in the IdP restores:

* **The membership level the person had before.** A guest comes back as a guest, and a member as a member.
* **Their seat**, for a member. A guest holds no seat.
* **Their team memberships**, re-applied from the groups your IdP holds for them now, so the person regains the gateways those teams reach.
* **An account an older SCIM deprovision had disabled.** SCIM re-provisioning never lifts a ban.

> [!WARNING]
>
> Don't restore a SCIM-managed member by inviting them again. An invitation restores them in MCP Manager while your IdP still lists them as deprovisioned, so the two disagree and the IdP no longer manages that person's access. Re-activate them in the IdP instead.

## Restore a member an administrator deactivated

A member an administrator deactivated is restored by inviting them again, which needs the **Invite users** capability.

**1. Open People → Users**

Go to [People → Users](https://app.mcpmanager.ai/settings/people/users) and select **Add new users**.

**2. Invite the member's email address**

Enter the member's email address under **Email addresses**, choose their role and teams, and send the invitation. Inviting an existing account restores its membership in this workspace; it does not create a second account.

**3. Check the member is back**

The person appears on People → Users again, and their AI clients work with their existing tokens.

Inviting a deactivated member restores them as a full member with a seat, even if they were a guest before, and applies the role and teams you chose in the invitation. Deactivation leaves a member's team memberships in place, so the teams they belonged to before still apply alongside the ones the invitation adds.

## Further reading

> [card] [SCIM Provisioning](https://docs.mcpmanager.ai/enterprise/scim.md)
>
> How your IdP creates, updates, and deactivates users, and maps IdP groups to teams.

> [card] [Teams](https://docs.mcpmanager.ai/deployment/teams.md)
>
> How team membership grants a member access to gateways.

> [card] [Capabilities](https://docs.mcpmanager.ai/deployment/rbac-and-roles/capabilities.md)
>
> The Invite users and Remove users capabilities, and every other permission a role can hold.

> [card] [Access Control](https://docs.mcpmanager.ai/deployment/access-control.md)
>
> How roles and teams combine into a member's access.


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