Access and onboarding

Start with an agreed engagement

Contact AutoBridge with a short description of the work, the intended users and any hosting or data constraints. AutoBridge and your team establish the scope, delivery approach and access arrangements before project work begins. There is no public self-service sign-up or build submission on this documentation site.

Prepare the starting package

• Name the sponsor, day-to-day product owner, technical contact and people who will accept the result.
• Describe the workflows, reports and integrations you need, with examples of successful outcomes.
• Identify approved source systems and data owners. Use synthetic or de-identified examples for early discussions.
• Record hosting, identity, accessibility and security requirements before implementation starts.
• Agree the initial milestone, review cadence and definition of done.

Separate the permissions

Permission to view an ADOM workspace does not, by itself, authorize access to a source repository, database, identity provider or production environment. Each system owner should approve the access needed for the agreed task. Technical onboarding should confirm the actual operations permitted, not just whether a connection succeeds.

First project review

Use the first review to walk through one representative workflow and its acceptance criteria. Confirm which environment will be used, which inputs are approved and what will happen when information is missing. Record unresolved dependencies with an owner and a next action.

If you cannot sign in or see the expected project, contact the person who provisioned your access. Include your work email, project name and the visible error. Do not include passwords, access codes or secret keys.