Skip to main content
Use these process rules whenever a change can affect secrets, access, production applications, or account billing.

​
Before you change a record

Confirm the project, record name, environment, and intended recipient before you reveal, edit, share, rotate, roll back, or archive a record. After a change, review History or Audit to confirm the expected event exists. Never use a screenshot as proof that a secret value was handled correctly.

​
Before you change access

Confirm the member or group, the role, and the projects or records affected. Apply the least access needed for the task. Review pending invitations and inactive members regularly. Do not remove or change the last required account owner as part of routine cleanup.

​
Before you change a gateway

Confirm the provider, project, model, and target application. Validate the provider connection before you create the gateway. Treat gateway deletion and provider-key changes as production-impacting changes.

​
Before you change billing

Review the plan, effective date, and any view-only consequence before you upgrade, downgrade, cancel, or reactivate a subscription.

​
When something looks wrong

Stop the change when a confirmation dialog, validation message, role restriction, or plan gate differs from what you expected. Re-check the project and your role before you try again. Use the relevant guide for the task, then contact support without including a passphrase, token, recovery code, record value, or provider key.

​
When reports a newer version

keeps the current page running while a newer Web or Admin build becomes available. A persistent update notice appears after the app verifies the newer build. The notice belongs to the tab that discovered the update. It remains visible while you continue navigating, but it never refreshes that tab or any other open tab automatically. If an older tab tries to submit an operation that the current API can no longer accept safely, rejects that operation before it changes data and changes the notice to Update required to continue. The form stays mounted so you can copy or otherwise preserve its unfinished contents. Read-only actions remain available. Save or copy any unfinished form before you select Update now. performs a full document refresh, returns to the same route, and keeps the existing sign-in session. Unsaved form input cannot survive that refresh. Other open tabs keep their current page and show their own update notice when needed. If you are offline or a deployment is still becoming ready, continue using the current page. checks again after connectivity returns and whenever you return to the tab.