Managed onboarding starts with a useful business task. Tell DigLab what should become easier, which systems hold the relevant information and which actions the AI may perform.
Information to prepare#
- Your business or team name and the authorised contact for setup.
- The AI application you want to use, including the relevant plan or workspace.
- The service accounts, brands and workspaces that should be connected.
- The first workflow, expected result and a harmless test record.
- Which operations may read data, create drafts or make changes.
- Any sensitive fields that should be excluded from results.
- Expected usage, relevant deadlines and the people who can approve changes.
Do not include passwords, API keys or recovery codes in an intake message. DigLab will agree the appropriate account authorisation or secure handoff route.
How setup progresses#
DigLab checks whether the required service has a supported integration route and whether your account has access to it. The connection is prepared with the agreed tools, then tested against your exact account. Untested additions are kept out of your active workflow.
When the test passes, you receive connection instructions and the scope of the working setup. An API being documented, a subscription being owned and a connection being tested are separate facts.
What a useful handoff contains#
The handoff should name the supported client, assigned endpoint, authentication method, enabled workflows, permission boundaries, expiry arrangements and support contact. It should also identify the first task used to verify success.
If a requested service is still pending, the handoff should say what remains unavailable and what is needed to finish it. Do not assume an example in this help center is included in your account.
After handoff#
Complete the quick start, check the account context and report any mismatch before using the workflow. New services, new destinations and broader write access are handled as explicit changes to your setup.