API keys and Doppler

An owner or admin manages credentials in Settings → Integrations. Every credential belongs to the selected company and either production or staging. Provider secrets belong here, away from shared knowledge, support messages and website embed code.

Store a credential in Summer#

1. Confirm the company and Environment.
2. Open a provider tile and select Add beside a field, or select Add credential below the tiles.
3. Use the exact variable Name from the provider setup. Names use uppercase letters, digits and underscores and begin with a letter.
4. Choose Store in Summer as the source.
5. Enter the secret in Value and select Save credential.

The saved list shows the credential’s name, source, updater and date. It hides the value. Required field counts update after saving; this is not a live check of the provider key.

Use the provider reference to identify required fields. An arbitrary credential name is stored as a credential but does not automatically connect a tool.

Reference an existing Doppler secret#

If your team already manages secrets in Doppler:

1. Under Bring your Doppler vault, select Connect Doppler.
2. Enter the exact Project and Config for this company and environment.
3. Enter a Read-only service token for that config. Summer does not accept personal or CLI tokens here. See Doppler’s service-token guide.
4. Select Verify and save. This checks the vault connection.
5. Open a credential editor, choose Reference Doppler, and enter the Doppler secret name. This may differ from the Summer credential’s name.
6. Save the reference. Summer reads its value when needed; secret values continue to be managed in Doppler.

Saving a Doppler reference checks that Summer can read that exact secret from the selected config. It does not test the key against its provider. Verify the provider account and required reads as part of the workflow setup.

To rotate the vault token, open Edit connection, enter a new token and verify it. To switch projects or configs, remove the existing Doppler credential references first. Summer does not edit your Doppler secrets.

Edit or rotate a provider key#

Select Edit beside the saved credential. For a Summer-stored credential, enter its Replacement value and save. Leaving that field blank keeps an existing stored value; restoring a removed credential or switching to Summer storage requires a value.

For a Doppler reference, update the secret in Doppler or edit the referenced secret name in Summer. Use the provider’s rotation procedure, verify the replacement with the required workflow, then revoke the obsolete key at the provider. If a key was exposed, follow your incident process and revoke it promptly.

If Summer reports that the record changed, reload the current settings before editing again. Avoid overwriting another administrator’s update.

Reveal, remove and audit#

Reveal displays a credential temporarily. It hides after 30 seconds or when page visibility changes. Reveals are recorded in Credential history, alongside saved changes. Use Hide to dismiss it sooner.

Remove stops Summer from using the saved credential. Removing a Doppler reference leaves the original vault secret intact. Disconnect Doppler makes its references unavailable until reconnection.

Removal from Summer does not revoke a key or an existing signed-in session at the provider. Revoke those at the provider when required. Removing a custom integration’s setup also leaves its credentials in the saved list; remove them separately if no longer needed.

If credential storage is unavailable, contact Summer to finish setup. Do not send a key through the help form or email. See Troubleshooting.