Generic Secrets is a source for values that Build and Plan can use in code and requests. It does not add documents to Search, connect an external account, or start an indexing job. The editor is the same secrets editor used in workspaces.
Add the source
An organization admin opens Settings → Sources → Add source → Generic Secrets and chooses one mode:
| Mode | Who manages the values | Who can use them in Build and Plan |
|---|---|---|
| Organization | Organization admins open Secrets from the source in Settings. | Organization members with Build access use the shared values. Members cannot open the editor to view them. |
| Member | Each person opens Integrations → Generic Secrets → Manage secrets. | That person uses only their own values in the organization. |
Only the selected mode is active. The admin can change it through Configure on the source. Removing the source deletes its organization and member secrets, so review the confirmation before doing so.
Use a secret in Build or Plan
Save a name and value in the editor, then ask Build or Plan to run code that needs it. These modes can see available names and mount only the names needed by run_code or run_function. The values become environment variables for that code, so it can use them in a request such as curl without putting the value in the prompt.
In an organization Build or Plan conversation targeting a workspace, an organization secret with the same name takes precedence over a workspace secret. In Member mode, the source resolves the current member's values; it does not read another member's secrets.
Generic Secrets are available only in Build and Plan modes. Search, the Search assistant, Search MCP, and Sim Search in Slack cannot mount them. Workspace secrets remain a separate resource.