3 Ways to Remove Users from Postman

Managing who can access your Postman assets is part of keeping APIs secure and collaboration clear. When someone changes teams or a project ends, you’ll want a clean way to remove their access without breaking work in progress.

This guide shows three practical options: remove a member from a workspace, remove them from the team, or deprovision through your identity provider with SCIM/SSO. We’ll note when each method applies and what it affects.

Table of Contents

• Use Postman's UI
• Use Torii
• Use Postman's API

Use Postman’s UI

Here, you’ll use the Postman UI to remove a user from your team. You must be a team admin to do this.

Before you start

• Check your role. You need to be a Team Admin or Super Admin.
• Removing a user frees the seat. It does not delete their personal Postman account.
• Postman’s docs note two related actions: Remove from team and Deactivate. Remove fully takes them off the team. Deactivate pauses their access without removing them.
• If the user owns shared resources, plan who should own them after removal.

Open Team Members

• In the Postman web or desktop app, select your avatar in the top right.
• Choose Team, then Members to open your team roster.

Remove the user from the team

• Find the person by name or email. Use the search bar if you have a long list.
• Open the three-dot menu next to their name.
• Select Remove from team.
• Confirm the removal when prompted.

Reassign owned resources if prompted

• If Postman asks you to transfer ownership:
  • Pick a new owner for collections, environments, monitors, and mock servers.
• Confirm to finish.

Remove someone from a single workspace instead

If you only want to remove their access to one workspace, not the whole team:

• Open the workspace and select the workspace name, then Settings.
• Go to Members.
• Next to the user, choose Remove from workspace. You can also change their role to Viewer if you just want to limit access.

Common gotchas

• If you do not see Remove from team, you might not be an admin, or the user is managed by your organization’s identity system. In that case, the option can be restricted.
• Pending invites show as “Invited.” Use the same Members page menu to cancel the invite.
• You cannot delete someone’s Postman account. You can only remove or deactivate them from your team or workspace.

Use Torii

Instead of handling this directly in Postman, you can use Torii, a SaaS Management Platform, to remove user in Postman. SMPs let teams manage SaaS subscriptions and integrations from a central place, making it simple to programmatically onboard/offboard users, view subscription details, and more.

Compared to doing it manually in Postman, Torii allows you to automate the task so it runs automatically whenever a trigger is met. Triggers could include a new hire, an employee offboarding, a contract renewal, etc. This can save time if you need to repeat the action regularly.

To remove user in Postman straight from Torii, follow these steps:

1. Sign up for Torii

Contact Torii, and ask for your free two-week proof-of-concept.

2. Connect your Postman account to Torii

After your account is active, connect Postman to Torii (assuming you already have an account). Here are the instructions for the Postman integration.

3. Create a Torii workflow for Postman

In Torii, build an automated workflow to remove user in Postman. Go to the Workflows tab, choose a trigger, and then add an action that removes the user in Postman. From then on, whenever the trigger occurs, Postman will be updated.

Use Postman’s API

Use Postman’s SCIM API to remove a user from your team. Here, you’ll look up the user by email, grab their SCIM id, then deprovision them.

Prepare your SCIM request details

You’ll call Postman’s SCIM 2.0 endpoints with a bearer token.

• Base URL to use: https://scim.getpostman.com/scim/v2
• Required header on every call:
  • Authorization: Bearer <SCIM_ACCESS_TOKEN>
  • Accept: application/scim+json
  • For write calls, add Content-Type: application/scim+json

Example environment variables to keep things tidy:

• SCIM_BASE=https://scim.getpostman.com/scim/v2
• SCIM_TOKEN=<SCIM_ACCESS_TOKEN>
• USER_EMAIL=<email_of_user_to_remove>

Find the user’s SCIM id by email

SCIM uses the user’s email as userName. Query it, then copy the id from the result.

Example curl is:

curl -s -X GET "$SCIM_BASE/Users?filter=userName%20eq%20%22$USER_EMAIL%22" \
-H "Authorization: Bearer $SCIM_TOKEN" \
-H "Accept: application/scim+json"

You should see a response with totalResults and a Resources array. Grab the id value from the first match.

Tip:

If totalResults is 0, check the email spelling. The filter must match .

Deprovision the user

Delete the SCIM user resource. This removes the user from your Postman team.

Example curl is:

curl -s -X DELETE "$SCIM_BASE/Users/" \
-H "Authorization: Bearer $SCIM_TOKEN"

What to expect:

A successful deletion returns HTTP 204 No Content.

Confirm the user is gone

You can re-check by id or by email filter.

Example curl is:

curl -s -X GET "$SCIM_BASE/Users/" \
-H "Authorization: Bearer $SCIM_TOKEN" \
-H "Accept: application/scim+json"

Or:

curl -s -X GET "$SCIM_BASE/Users?filter=userName%20eq%20%22$USER_EMAIL%22" \
-H "Authorization: Bearer $SCIM_TOKEN" \
-H "Accept: application/scim+json"

Expected results:

• GET by id should return 404 after deletion.
• GET by email should return totalResults: 0.

Quick troubleshooting

• 401 or 403: the SCIM token is missing or lacks permission.
• 200 with no Resources: the email didn’t match any user.
• 409 or 429: retry after a short pause. Some org policies can throttle or block deletes.