Report

List everything a Postman member owns before they leave

For API team leads who need a handover list of a Postman member's workspaces, collections, environments and monitors, ranked by risk.

Review a Postman member's ownership for handover

Jordan Lee is leaving next week. What does he own in Postman?

Jordan Lee owns 23 items in Postman, 5 of them high risk. - Active monitors: 3, including Payments nightly on Production - Public: 1 collection and 1 environment - Workspaces created: 2 team workspaces Want the full handover checklist?

Postman

Sample figures. Your results come from your own account.

postman-get-users

postman-get-workspaces

postman-get-collections

postman-get-environments

postman-get-monitors

postman-get-collection-comments

On this page

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Postman

Run it on your own Postman data.

Connect Postman, pick your AI tool and paste the prompt.

The problem

Nobody knows what a leaver owns in Postman

When someone leaves the team or changes role, nobody has a list of what they own in Postman. Their monitors may stop when their account goes, their public collections lose an owner, and their team workspaces are left without an admin.

Without PopdockAI

Search workspaces for ones they created
Check owners on collections and environments
Find the monitors they own
Discover a stopped monitor after they leave

With PopdockAI

The member is found by name, username or email
Their workspaces, collections, environments and monitors are collected
Findings are ranked by risk, active monitors first
A handover checklist, with nothing changed

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt

**Objective:** Build a handover list of everything owned or created by the team member `{member}` (name, username or email), so it can be reassigned before they leave or change role.

**Step 1: Resolve the member**

Call `postman-get-users`: use `email` if `{member}` contains @, otherwise try `username`, then `name`, then `name.contains`. If more than one user matches, list name, username, email and joined-at and ask which. Keep user-id.

**Step 2: Collect what they own**

* `postman-get-workspaces` with `created-by` = user-id.
* `postman-get-collections` with `owner` = user-id. Mark forks (forked-from-collection-id set) separately.
* `postman-get-environments` with `owner` = user-id.
* `postman-get-monitors` with `owner` = user-id. Name each monitor's collection and environment by matching collection-uid and environment-uid against the collections and environments read above (read the full lists if needed).
* `postman-get-collection-comments` with `created-by` = user-id and `created-at.from` = 30 days ago, to show open conversations they are part of.

**Step 3: Assess risk**

* Active monitors they own are the highest risk: if the owner's account goes, scheduled runs may stop.
* Public environments and public collections they own come next.
* Team workspaces they created need a new admin.
* Personal forks are usually safe to drop or merge.

**Step 4: Report**

One section per resource type in the order above, each a table with name, key status (active, public, visibility) and last updated where available. End with a short handover checklist.

**Rules & Guidelines:**

* This is read-only. Do NOT call any add, update, run, fork, merge, publish or comment tool, including `postman-update-workspace`, `postman-update-monitor` and `postman-add-collection-comment`.
* Owner filters take the user id. If a filter returns nothing but the member clearly owns things, say the owner field may hold a different id and show the raw owner values seen.

**Validation:**

* If no user matches `{member}`, list users whose name contains part of it and stop.

Who it's for

One answer, three teams that use it

IT administrators

Offboard without breaking monitors

Active monitors a leaver owns come first, so you can move them before the account goes.

Priya Shah leaves Friday. What does she own in Postman?

Engineering managers

Plan a role change

Get a checklist of what to hand over when someone moves team.

List everything tom@contoso.com owns in Postman, ranked by risk.

Workspace admins

Keep public assets owned

Public collections and environments a member owns are listed, so they get a new owner.

Which public Postman collections and environments does Alex Kim own?

How it works

What PopdockAI does when you ask

You name the team member and your AI assistant collects everything they own in Postman. It ranks it by risk, ends with a checklist and changes nothing.

Ask

You name the team member by name, username or email.

Your AI tool

Collect

It gathers their workspaces, collections, environments, monitors and recent threads.

postman-get-users

postman-get-workspaces

postman-get-collections

postman-get-environments

postman-get-monitors

postman-get-collection-comments

Rank

It ranks findings by risk, active monitors first.

No items found.

Report

You get a handover checklist, and nothing is changed.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Postman and one secure connection to your AI tool. No code, no exports.

get-data

postman-get-users

Returns the members of a Postman team with their name, username, email and join date. Filter by name, username or email.

get-data

postman-get-workspaces

Returns Postman workspaces with their name, type, visibility, description and creator. Filter by name or by the user who created them.

get-data

postman-get-collections

Returns Postman collections with their owner, ids, last update and fork details (parent collection, fork label, fork date). Filter by name, collection id or owner.

get-data

postman-get-environments

Returns Postman environments with their name, ids, owner, whether they are public and when they were last updated. Filter by name or owner.

get-data

postman-get-monitors

Returns Postman monitors with the collection and environment each one runs, its owner and whether it is active. Filter by name, collection or owner.

get-data

postman-get-collection-comments

Returns comments left on Postman collections, with thread, author and dates. Filter by collection name, comment text, thread, author or creation date.

Read only.Nothing in Postman Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

The outcome

A risk-ranked handover list before anyone leaves

Related use cases

More ways to put this data to work

Change a Postman monitor schedule

Ask your AI to change a Postman monitor's schedule or name and it checks the cron expression, reads it back in plain words and updates only after you confirm.

Learn More

Publish or unpublish Postman collection docs

Ask your AI to publish or unpublish Postman collection docs and it checks for secret-like variables or a breaking link first, acting once after you confirm.

Learn More

Run monitors for a Postman collection

Ask your AI to run a Postman collection's monitors and it lists active and paused ones, then starts each active monitor once after you confirm.

Learn More

Schedule a Postman collection monitor

Ask your AI to schedule a Postman monitor and it checks for an existing one, reads the cron schedule back in plain words and creates it after you confirm.

Learn More

Set up a Postman API project

Ask your AI to set up a Postman API project and it checks what exists, then creates only the missing workspace, collection and environments after you confirm.

Learn More

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.