# How to onboard a new Salesforce client org in days, not weeks. > Onboarding a client org with SyncOnAI 360 means connecting it with OAuth, letting the sync, health score and audit establish a baseline, sharing that baseline read-only, setting the org's conventions, deploy policy and freeze windows, inviting the client's admin as approver, and starting work through governed proposals. Source: https://synconai360.com/use-cases/client-onboarding ## Key facts - **Day 1**: Health and audit baseline - **Per org**: Conventions and freeze windows - **0**: Accounts the client needs to see the baseline - **1**: Governed path from the first change ## Why client onboarding drags on A new client means weeks of access requests, walkthroughs and spreadsheets before anyone can safely change anything. - **Walkthroughs.** Hours of screen shares to learn the org. - **No baseline.** Nobody records the org's state on day one. - **Unknown rules.** The client's conventions and change windows are tribal knowledge. - **Early mistakes.** The first changes are the riskiest. ## How do you connect a new client org? The client authorises the org, or a sandbox first, with Salesforce OAuth. The first sync runs in the background with progress by stage; later syncs are incremental and run every six hours. - OAuth connection - Background sync - Six-hour refresh ## How do you record the starting point? The health score with its confidence and coverage, and the audit with evidenced findings and costs, form the baseline. Review history keeps it, so every later review compares against day one. Share it with the client as a read-only link. - Health and audit baseline - Kept for comparison - Shared read-only ## How do you capture the client's rules? Set org rules for naming conventions, forbidden patterns and the preferred automation type, so the AI builds inside them. Set the deploy policy's freeze windows and required approvers to match the client's change calendar. - Conventions as rules - Freeze windows - Required approvers ## Who should be in the workspace? Invite your consultants as members and the client's admin as an admin, so production changes can be approved by someone other than their author. Roles are chosen at invitation. - Consultants as members - Client admin as approver - Roles at invitation ## How do you start working safely? Turn the first findings into work items, draft fixes with the AI or builders, and ship them as proposals with checks, validation and approval. Every deploy leaves a receipt with rollback. - Findings to work - Governed first changes - Receipts from day one ## What should the first month look like? Week one: connect, baseline and set the rules. Week two: fix the severe, quick findings and share a re-audit. Weeks three and four: plan the larger items as work items or a statement of work, and start the regular reporting rhythm. By the end of the month the client has seen evidence of progress against their own baseline. - Baseline in week one - Quick wins in week two - A rhythm by week four ## How to onboard a client org 1. **Connect.** OAuth to a sandbox, then production. 2. **Baseline.** Health and audit, shared read-only. 3. **Set rules.** Conventions, freeze windows, approvers. 4. **Invite.** Consultants and the client's admin. 5. **Start.** First fixes through proposals. ## Client onboarding, slow versus structured | Without | With SyncOnAI 360 | |---|---| | Weeks of walkthroughs | The org synced and explained | | No record of the starting point | A shared baseline | | Conventions as tribal knowledge | Org rules | | Risky first changes | Governed from day one | ## Client onboarding checklist - [ ] Have the client authorise a sandbox, then production. - [ ] Wait for the first sync and record the health and audit baseline. - [ ] Share the baseline as a read-only link. - [ ] Capture the client's conventions as org rules. - [ ] Set freeze windows and required approvers to match their change calendar. - [ ] Invite consultants as members and the client's admin as approver. - [ ] Turn the first findings into work and ship the first fixes. ## Who onboards client orgs - **Managed services providers.** Take on a new client in the first week. - **Consultancies.** Start every engagement from a baseline. - **Independent consultants.** Look organised from the first call. ## Frequently asked questions ### What does the client need to do? Authorise the org with Salesforce OAuth, and join the workspace if they will approve changes. ### Can we start on a sandbox? Yes. ### Is client data stored? No CRM records are stored; only metadata. ### Can the client see the baseline? Yes, as a read-only report link. ### Can we match the client's change calendar? Yes, with freeze windows in the deploy policy. ### Can the client's admin approve our changes? Yes, as an admin in the workspace. ### Can we offboard later? Disconnect the org and withdraw any shared links. ### Is this on every plan? Yes. Every plan includes every feature. ### Can we keep the client's documents with the org? Yes. Runbooks and meeting notes are pages beside the org. ### How long does onboarding take? The first sync takes minutes; most teams have a baseline, rules and approvers in place within the first week. ### Does the client need training? Not to read reports, which open without an account. Approvers see each proposal's checks in plain language. ### Can we onboard several clients in parallel? Yes. Each client org is connected, baselined and governed on its own. ### What if the client has no sandbox? Connect production; exploring and auditing never change it, and changes always go through proposals. ### What should we share with the client in week one? The read-only baseline report, so both sides agree from the start where the org stands today.