Regenerate

If you lose your access key or believe it was seen by someone else, you can generate a new one from the admin panel. The moment a new key is issued, the previous key stops working at the login form.

When to regenerate

There are three situations where regenerating makes sense. The first is losing your key — you cannot find it in your password manager, your notes app, or anywhere else you might have stored it. The second is a suspected exposure — the key appeared somewhere public (a Git commit, a shared document, a screenshot posted online) and someone else may have seen it. The third is routine rotation — if your organization's security policy requires credential rotation on a schedule, regeneration is how you do it.

Regenerating when you still have the current key is safe. The new key appears on screen the moment you regenerate, giving you a window to copy it before the old key expires. However, once you submit the regeneration request, the old key becomes invalid immediately — even if you have not yet copied the new one. Save the new key before closing or navigating from the confirmation screen.

How to regenerate

Log into the admin panel with your current access key. Navigate to the account or security settings section. Find the option labeled regenerate access key or similar. The system will ask you to confirm the action, since it cannot be reversed: the old key will not work after this point.

After you confirm, the new 32-character access key appears on screen exactly once — the same one-time display as after your initial checkout. Copy it to your password manager immediately. Do not close the tab, navigate away, or switch applications until the key is safely stored.

If you cannot log in with your current key because it was already lost, you cannot use the self-serve regeneration flow. In that case, contact support with information that verifies your account ownership. The support process exists precisely for this situation — losing an access key is recoverable, it just requires an out-of-band identity check.

What changes and what stays the same

Regenerating your access key changes only your login credential. Your sites, their registered domains, their site keys, and all historical visit count data remain exactly as they were. The dashboard you see after logging in with the new key is identical to the dashboard you would have seen with the old key.

All existing dashboard sessions — tabs in other browsers or on other devices where you were previously logged in — become invalid when the access key is regenerated. Those tabs will show the login form on their next request to the dashboard. Log in again with the new key on each device where you need access.

The site keys used by asset.js in your tracking script tags are not affected by regenerating your access key. Site keys are separate identifiers with a separate lifecycle. Your tracking scripts continue to fire beacons and record visits without any change after a key regeneration.

After you have the new key

Store the new key in your password manager before doing anything else. Then log in with it on each device or browser where you use the dashboard. Delete any old copies of the previous key — in notes, text files, or emails — to avoid future confusion about which string is current.

If the old key was exposed and you regenerated to protect the account, consider reviewing recent dashboard activity to check for any unexpected changes to your settings or registered sites. A session established with the old key before you regenerated would have expired by the time any session-based access is attempted after the key is invalidated.

Troubleshooting

If you completed regeneration and immediately navigated away from the confirmation page before copying the new key, you are locked out of the self-serve flow and need to contact support. There is no second display of the new key after the confirmation page is left. This is the same behavior as the initial account creation — the key is shown once.

If you regenerated and your existing dashboard tabs are still showing the old session without asking you to log in again, this is normal browser caching behavior. Those tabs will ask for the new key the next time the session is checked — either on navigation, after inactivity, or on browser restart. The old key is invalid for any new login attempt immediately after regeneration, even if existing sessions have not expired yet.