Use this workflow when an existing application or project needs a supported secret runtime variable. The AI prepares a link and checks progress; you type the value in an authenticated portal page. Never send the value to the AI or in tool arguments.
Before you start
- An existing app or project owned by your account, and the target variable’s name.
- Owner access to the portal, including Tor Browser when using an onion entry link.
- A connector offering
impreza_prepare_secret_entryandimpreza_get_secret_entry: current hosted MCP or local 0.49.0+. - The permissions needed for the target and the later redeploy. A new MCP package does not install or update your server’s Agent.
This form changes a supported runtime variable. For initial catalog installation, Git-access credentials, build-secret rotation, host passwords or onion-key import, use the relevant portal form instead.
Distinguish generated login details from private input
The account owner can open My Apps → Login details to view platform-managed credentials available for that deployment. Depending on the app, these can include an admin login, a database password, an API key or a gateway token. The card does not know a password you create in the app’s own browser setup. Use the first-deploy guide to check that distinction before signing in.
For supported API/MCP creation responses, generated credential values are returned in the designated creation result; structured metadata may identify the keys and direct you to the text result. A mask such as ******** is not a usable password. Do not ask the assistant to repeat a secret into the conversation: for direct owner access, use Login details and keep the value in your private password manager. A value already returned to an AI client is not made private by using this entry form later.
Team access is separate from ownership. Sensitive login values are reserved for the account owner; app-changing controls also depend on the member’s management permission. Having permission to view services does not grant every secret or action. These portal controls are separate from the scopes and restrictions on an MCP credential.
The form below serves a different purpose: you provide a supported runtime secret to an existing app without passing its value through the assistant. It does not rotate the app’s own login password automatically, create the first owner account or recover an MCP token.
1. Ask for the entry link
Identify the deployment and variable name, or the project and optional environment. Do not include the value. For example: “Prepare secret entry for the API_TOKEN runtime variable on this app; I will enter the value in the portal.” The assistant uses impreza_prepare_secret_entry and receives a short-lived entry session.
2. Verify the target and enter the value
Open the returned portal link yourself. Sign in as the same account’s owner and check the app, project/environment and variable displayed. Cancel if the target is wrong. Enter and submit the value only on that page.
The link can be consumed once and expires after ten minutes. Do not share it. Its token is kept in the URL fragment and removed by the page, rather than being sent in the HTTP URL or referrer. The page loads no third-party resources. This does not prevent browser extensions or a compromised device from reading what you enter.
3. Let the assistant read the status
With impreza_get_secret_entry, the assistant sees the session ID, variable name and pending, stored, expired or cancelled status. It receives neither the value nor its hash. If expired or cancelled, prepare another link instead of pasting the value into chat.
4. Apply and verify
Redeploy to apply the stored value. Review the operation, wait for completion and verify the application’s actual connection or request. A stored status does not prove that the credential works. Group values retain their normal project → environment → app precedence.
Supported Git webhook redeploys, image promotions and configuration applies preserve stored secrets. Exports use secret references: keep those references when editing configuration. To rotate a value, prepare a fresh owner entry link.
If you already sent a secret to the AI
Rotate it. A later tool refusal cannot remove it from the provider’s conversation history. Secret classification is not a general scan of arbitrary code or unrecognized fields. Use authenticated portal forms/uploads for sensitive material rather than testing whether a chat tool will reject it.
Read the technical secret-entry reference for supported targets and REST routes. For the commercial overview, see AI deployments with private secret entry.