Treat a connection key as access to the operations it permits. The endpoint identifies the connection; the credential proves access. Keep both within the agreed team and delivery process.
Store and enter keys safely#
Use the client's supported secret input or approved credential storage. Do not put a raw key into a prompt, a support ticket, a shared document, a screenshot or a public configuration file. Do not add it to a URL: URLs can appear in browser history, logs and copied links.
Examples in these docs use placeholders. They contain no working credentials. DigLab will deliver real connection details through the secure route agreed during onboarding.
Choose the minimum data needed#
Ask for only the fields and date range necessary for the task. Tool results are returned to the AI application you use, so that application's account settings and data policies also matter. Check your organisation's rules before processing personal, confidential or regulated information.
The documentation website does not need you to enter a connection key. Its search runs against the published help articles in your browser. It does not search your business records.
Redact before contacting support#
Include the error code, tool name, time and a short description of what you expected. Remove keys, authorisation headers, cookies, personal data and unnecessary business records from evidence. Check attached files as well as the visible message.
If a key may have been exposed#
Stop using the exposed credential and contact DigLab through your established support route. State where it may have appeared without pasting the key again. DigLab can arrange revocation, replacement and a connection check. Deleting a message containing a key does not establish that the credential is safe to keep using.