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

# Set an integration's visibility

> Choose whether an integration is public on Pomerado or private to your team.

An integration's `visibility` says who can find and run its tools.

| Visibility | Who sees it |
| - | - |
| `public` | Every Pomerado account can find and run its tools |
| `private` | Only your team's members see, run and edit its tools |

A website can have a public integration and your team's private one side by side, each with its own MCP URL.

## Business accounts

A Business account's integrations start private. To publish one, change it on the integration's page on the Dashboard, or send the new visibility:

```http theme={null}
PUT /v1/integrations/{id}/visibility
Content-Type: application/json

{ "visibility": "public" }
```

Through the Pomerado MCP, call `call_pomerado_api` with `integrations.update`. An Owner or Admin changes every tool the team built in the integration; a Member changes only their own. See [Roles and invitations](/guides/teams/roles-and-invitations).

## Personal accounts

You can't change visibility. When a tool is first published, Pomerado reviews its website: if the review can't confirm the site is safe to list publicly, the tool stays private to you, and otherwise it is public. A later revision keeps the tool's visibility.

<Accordion title="Details">
  * Changing visibility moves your team's tools into the website's integration of that visibility. Its ID can change, so use the `id` the answer gives.
  * Tools other accounts built in a public integration stay public when you make yours private.
  * When the integration your tools would join already has a tool of the same name, the change is refused with `integration_tool_name_taken`. There is no way to rename a tool; delete one of the two with `DELETE /v1/tools/{id}`, then try again.
  * A public integration also has a keyless URL for use without signing in. See [Connect an integration MCP](/guides/integration-mcps/connect).
</Accordion>


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