Allow Vamo in a Claude Team or Enterprise workspace

A Claude Team or Enterprise workspace needs one thing allowed for Vamo: members adding custom connectors. If members will also use Vamo skills, Claude's sandbox must be allowed to reach api.vamotalent.ai. Only an org owner can change that second setting.

The ways your members can connect

There are two, and each depends on a different workspace control.

A connector. A member adds Vamo to Claude as a custom connector. Claude opens a Vamo page, the member approves, and Claude is connected. No API key is handled. Claude Desktop can also connect with a key.

Skills. Skills are instructions Claude reads. They call the Vamo API directly with the member's own API key. They do not use the connector.

Which one we recommend

Start with the connector. It suits most teams, and nobody handles a key.

Add skills when your members want Claude to follow Vamo's own search methods. A connector and skills can sit side by side.

What must be allowed

Custom connectors. Vamo is added as a custom connector. If your workspace does not let members add their own, they cannot connect.

The sandbox reaching the Vamo API host, for skills only. Vamo skills need Claude's sandbox allowed to reach api.vamotalent.ai. A Vamo connector is not subject to this setting.

If your network also filters traffic, Hosts to allow covers what Vamo needs.

What Vamo can access

A connected tool acts inside one Vamo account. It can search for developers, run research, and work with lists and contacts.

It can never reach projects, outreach, members, billing or key management. The connector cannot read account, usage or billing information.

A member who signs in gets the search and enrich permissions by default. A key has the permissions chosen when it was created.

What Vamo can access has the full picture for a security review.

Who to involve

• A Claude org owner. Only an org owner can allow the sandbox to reach the Vamo API host.
• Whoever controls connectors in your Claude workspace. They decide whether members can add Vamo.
• A Vamo owner or admin. They see every connected tool on the account and can remove any of them.
• Each member. Every person approves their own sign-in. Their Vamo role must be owner, admin or user. A read-only member cannot.

The Vamo account must be on a Pro or Enterprise plan. Approving a sign-in and creating a key both need one.

Where to get the current steps

Claude's settings change, so this page does not describe where each control lives.

For the Vamo side, members open the Set up > Get started at Set up > Get started. It gives the current address to add as a connector. For skills, they follow the skills install page.

Connect Claude to Vamo is the page to send your members.

What a first good result looks like

Ask one member to connect and start a new conversation. For example:

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

A good answer names real developers and says what each has built. Claude then appears under Connected tools at Set up > API keys, with who approved it.

What commonly goes wrong

• A member cannot add Vamo. Custom connectors are not allowed for them. See Can't add Vamo.
• The connector works but skills say the network is blocked. The sandbox cannot reach the Vamo API host. An org owner must allow it.
• The Vamo page will not let a member approve. Their plan or role may not include it. See Sign-in fails or plan not included.

If something is not working