Access should change when the people, devices or business scope change. Ask DigLab to review the connection when a teammate leaves, a device is lost or a credential may have been exposed.
Replace a credential#
Use the established support route to request a replacement for the correct organisation and connection. The replacement should be delivered securely and tested with the agreed client. After the authorised handoff, the old credential should be revoked and checked to ensure it can no longer connect.
Do not paste the old key into the request. Identify the connection through the non-secret reference in your handoff.
Move to a new device#
Install or use the supported AI application and follow its organisation policy. Confirm how credentials should be delivered or stored on the new device. Do not copy a full browser profile, unrelated password store or another person's configuration as a shortcut.
Expired or revoked access#
If a previously working connection now rejects authentication, contact DigLab with the time and error stage. A rejected credential may be an intentional security action. Do not attempt to restore access by using someone else's key.
End a service#
Agree the end date, affected accounts, required record retention and any approved handover. Disabling an MCP connection is separate from deleting data in the business service. Do not assume that offboarding should erase business records.
After access is withdrawn, remove the obsolete connection from your AI client using its normal controls. Keep only the documentation and business records your organisation is entitled to retain.