Keep access working
Use the expires_in value from the token response to renew a bearer token before it expires. A client-credentials grant has no refresh token: request another access token with the same environment's client ID and secret. Cache the token in memory and retry temporary token-service failures with backoff.
If a client secret is lost or exposed, open System integration in the Portal, use the Environment switch to choose the affected side, and select Rotate credentials at the bottom of the credentials panel. Confirm with Rotate Sandbox keys or Rotate Live keys. The new secret appears in the panel once: store it immediately, update your system, request a new token, and make an approved read. The previous secret stops working the moment you confirm, with no overlap period, so agree the moment with whoever runs the systems still using it. Sandbox and Live credentials are independent, and the client ID does not change. The steps are in Your workspace.
A suspended organisation cannot rotate its credentials. The workspace shows Access is suspended with the reason the Secretariat recorded, and ITS refuses a rotation until the Secretariat restores access.
If access is refused after a successful token request, check token issuer, audience (its-core-sandbox or its-core-live), expiry, organisation state and the operation's permission. The Secretariat can review admission, participation, delegation, Live approval, and whether access has been suspended. Report a correlation ID and the failed method/path, without secrets or tokens.