ChatGPT Business and Enterprise: what admins allow for Vamo

On a ChatGPT Business or Enterprise workspace, an admin may need to allow Vamo before members can add it. Vamo is added as a connector, approved by signing in to Vamo with a browser. The workspace may also keep an approved snapshot of Vamo's tools, which the admin refreshes when Vamo changes them.

How ChatGPT connects to Vamo

The Pick your tool section offers one way for ChatGPT: sign in with your browser. A member adds Vamo as a connector. ChatGPT opens a Vamo page, the member approves, and ChatGPT is connected. No API key is handled.

We recommend this for every ChatGPT workspace. Connect ChatGPT to Vamo covers the member's side.

What the admin allows

Two things have to be true on the workspace.

Members can add Vamo. Some workspaces do not let members add their own connectors. If yours is one, a member cannot add Vamo until an admin allows it. Can't add Vamo describes what the member sees.

ChatGPT can reach Vamo. The connector lives at mcp.vamotalent.ai.

What you need on the Vamo side

• A Vamo account on a Pro or Enterprise plan. Approving a sign-in needs one.
• A Vamo role that can create keys: owner, admin or user. A read-only member cannot approve a sign-in.
• The current connector address. It is written by the Pick your tool section at Set up by hand.

Where to get the current steps

The steps change as ChatGPT changes, so this article does not repeat them.

Open Set up > Get started in the Vamo app and choose ChatGPT. That section gives the address to add and says what to do with it.

What you are approving

An admin approving Vamo can tell their security team the following.

• A signed-in tool gets the search and enrich permissions by default.
• A signed-in tool can only ever hold search, research, fit ranking, lists and contacts.
• It can never reach projects, outreach, members, billing or key management.
• It cannot read account, usage or billing information.
• Vamo owners and admins see every connected tool at Set up > API keys, with who approved each.
• Removing a tool there disconnects it.

When Vamo changes its tools

Vamo changes its tools from time to time. A workspace may hold an approved snapshot of the tool list. The snapshot does not follow the change on its own.

When that happens, Vamo worked before and now a member's assistant cannot see the Vamo tools. The fix belongs to the admin: refresh the Vamo tool list for the workspace.

Vamo tools are missing covers the same symptom from the member's side.

What a first good result looks like

After the admin allows Vamo, a member connects and starts a new conversation. For example:

Use Vamo to find the strongest engineers at <company>.

A good answer names real developers, says what each has built, and says why they fit. ChatGPT then appears under Connected tools at Set up > API keys.

What commonly goes wrong

• A member cannot add Vamo. The workspace does not allow it yet. See Can't add Vamo.
• The Vamo page will not let a member approve. Their Vamo plan or role may not include it. See Sign-in fails or plan not included.
• Vamo worked, then the tools went missing. The approved tool list may be out of date. See the section above.
• A member is asked to sign in again. A signed-in tool must sign in again after 90 days without use.

If something is not working