Browsers, credentials & integrations

When Embodiments need websites, signed-in accounts, or external services, enable tools only for Offices that need them. Browsers are configured per Office. External accounts and integrations are centralized in Organization › Connections & credentials. The organization's Veinmesh key is under Organization › Services & integrations. Your own Edgewright and Veinmesh keys are Your keys on Me, and Services in the navigation. None of them are on this page.

Enable Office services

An Office checking a supplier portal needs a browser; one discussing internal proposals can leave it off.

1. Open the Office’s Settings › Services.
2. Enable Office browser or a connected integration.
3. If Edgewright research engine is available, enable it here. The system first opens or confirms this Office’s research workspace.

Enabling the browser adds a Browser tab. Browsers and research are off by default in new Offices. Disabling research removes access, not the research workspace’s history. See What is Edgewright?.

Give each Embodiment its own browser

Use seat browsers when two Embodiments need different accounts on the same website, keeping their sign-in states separate.

1. Enable Office browser first.
2. If Seat browsers, one per member appears, enable it. “Member” in this label means an Embodiment in the Office.

Each Embodiment then operates its own browser with a separate profile and sign-in state. When disabled, Embodiments share the Office’s sign-in state. The seat switch appears only when the browser is enabled and the server provides this feature.

Watch and take control of the browser

Watch how an Embodiment works, then take over to select the correct order or add missing information.

1. Open Browser in the Office. Watching alone does not give you control.
2. With seat browsers, choose an Embodiment from the Browser menu above. Choose Shared for the Office’s shared browser.
3. Select Take control. You can enter URLs, click, type, and scroll. A control countdown appears.
4. Select Release when finished. Control also returns automatically after 15 idle minutes. Each action extends the time again.

Embodiments stop operating the browser you control; other seats are unaffected. If someone else controls it, the screen shows their name and you cannot take it directly from them.

Store a website password or API token

Put accounts in the vault, then grant access to Embodiments instead of pasting passwords into conversations. An API token is a secret account identifier for API calls, not a website password.

1. Open Organization › Connections & credentials and select Vault under Credentials.
2. Enter Slug, Display name, and the full Site url, such as https://support.example.com.
3. Choose Kind:
   • password: enter password and, if needed, Username.
   • API token (server-side API calls): enter Token. Username is optional and only distinguishes accounts.
4. Select Create.

The credential appears in the list. Next, grant it to an Embodiment.

Grant a credential to an Embodiment

For example, grant a supplier account only to the Embodiment checking orders and explain what it should use it for.

1. Expand Grants on the credential.
2. Choose an Embodiment under Grant to and enter Purpose, such as “Check this quarter’s order delivery dates; do not modify orders.”
3. Select Grant.

The list shows the Embodiment, purpose, and grant time. When an Embodiment lists its credentials, it sees only slug, display name, site URL, username, and purpose—not passwords or tokens. The system fills passwords into the browser. Soulhall sends API tokens in a Bearer Authorization header; the Embodiment reads the service’s reply.

Update a vault password or token

After changing an external account’s password or token, update its vault value too.

1. Select Rotate password on the credential.
2. Enter the new value under New password and select Rotate. For an API token, use the same action and enter the new token.

You see Rotated. This updates only the vault, not the external website’s password. The interface still says “password” even for API tokens.

Revoke a grant or delete a credential

When work ends, expand Grants and select Revoke beside the Embodiment to remove its authorization.

If the whole credential is no longer needed, select Delete and confirm. This removes the credential, active grants, and stored secret—not just one Embodiment’s access.

Connect tools from an external service

If a project-tracking service offers ticket-search tools, connect it once, then choose which Offices can use it.

1. Open Organization › Connections & credentials and select Connect under Integrations.
2. Enter Service id (lowercase, dashes), Display name, and MCP endpoint URL. The last field is the service’s tool connection URL.
3. Choose a connection method:
   • Sign in (OAuth): select Create, authorize on the service’s own sign-in page, then return to Soulhall.
   • API key: enter API key and Header name (default Authorization), then select Create. A blank header name sends Authorization: Bearer …. A different name puts the key directly in that header.
4. Confirm Connected, then expand Tools to review what it provides.

Tool names appear as serviceid__toolname. If you see Waiting for authorisation or Connection error, finish authorization or resolve the listed issue before enabling it in an Office.

Enable an integration in an Office or disconnect it

1. Open the Office that needs it, go to Settings › Services, and enable the integration.
2. When the external service adds or changes tools, select Refresh tools on the integration in Organization › Connections & credentials.
3. When the whole organization no longer needs it, select Disconnect.

Tools are available only when the integration is connected and enabled in that Office. Disconnecting removes the organization integration, tool list, and Office switches—not just access in one Office.

Related pages

• Veinmesh data
• Offices
• Telegram
• Models & spend
• Data & security