Application keys

Use the key overview in Settings to find credentials that need attention. Make credential changes in the application that owns the key.

Review the overview

The page counts active keys, keys needing attention, and retired keys within your access. Attention can mean an approaching expiry, a rotation in progress, or a previous key that is still within its expiry period.

Select Open beside an entry to reach its application settings. The overview shows up to five entries needing attention. Use Open applications to review additional applications and their keys.

If the page cannot load keys, refresh it before relying on the status. A loading error does not mean no keys exist.

Manage an application key

Open Applications and select the intended application.
Choose Config → Keys. Developers see the key as soon as they open Config.
Check the application name, environment, and current key status.
Use the available issue, rotate, or revoke action for the required change.

Administrators and authorized Developers manage application keys. Demo and sandbox mode do not permit key changes.

Copy a newly issued or rotated key directly to your approved secret manager. The complete value is shown once. Do not put it in source code, logs, or browser code.

Coordinate rotation and revocation

Before a planned rotation, check when the previous key stops working and arrange the application update with its owner. Verify the replacement in the intended environment. Do not assume a rotation gives an unlimited overlap period.

Revocation stops authentication with the revoked key. If a key is exposed, follow your incident procedure rather than waiting for routine maintenance.

Read Manage application credentials for storage, rotation, and exposure-response guidance.