Skip to main content
A team-shared custom toolkit makes a toolkit and its tools available to active members of the owner’s current Neo team. The owner keeps control of the toolkit definition and chooses how required credentials are supplied. The standalone global toolkit remains personal and cannot be shared. Create a named toolkit for tools your team needs to use.

​
Choose how credentials are supplied

Every shared toolkit uses one credential mode: In shared mode, teammates execute the toolkit with the owner’s bound credentials inside their own sandboxes. Treat anyone who can execute the toolkit as able to use those credentials in that environment. The API never returns secret values, and only the owner can see the saved-secret IDs used as bindings.

​
Share a toolkit with Neo

For personal credentials, ask Neo:
For owner-provided shared credentials, name the saved secrets and explicitly authorize their use:
Shared mode requires a saved secret for every environment variable the toolkit declares. Give Neo secret names only, never secret values.

​
Share a toolkit through the API

Use personal mode when every caller supplies their own credentials:
Use shared mode to bind the owner’s saved secrets. Map each required environment-variable name to its saved secret ID:
The first sharing request requires credential_mode. On later requests, omitted fields keep their current values. Supplying secret_bindings replaces all existing bindings. Switching to personal mode clears the shared bindings but does not delete the owner’s saved secrets. The API determines the owner’s active team. Do not send a team ID.

​
Discover and use shared toolkits

Ask Neo to list or use the team’s toolkits:
Through the API, list both owned and accessible team-shared toolkits:
Shared entries use team-prefixed identifiers when needed to avoid collisions with personal tools. Use the exact toolkit or tool identifier returned by Neo or the API when attaching or running it. The response reports credential readiness without returning values:

​
Stop sharing

The owner or an active team administrator can ask Neo to revoke access:
Or call the API:
Revoking access removes the team share and its credential bindings. It does not delete the toolkit or the owner’s saved secrets. Future execution is blocked after sharing is revoked, a member is offboarded, or a bound secret is deleted. A call already in progress is not cancelled. Replacing a deleted secret with another secret of the same name does not restore the binding. The owner must bind the new saved secret explicitly. For complete request and response schemas, see the API reference.