Getting started with OrgBolt
Your first fifteen minutes with OrgBolt: sign up, connect a sandbox, describe a change in plain English, and watch it get validated and deployed.
1. Sign up and pick your experience level
OrgBolt is a chat-first change manager for Salesforce. You describe a change in plain English, the AI turns it into a Work Turn (a generated, read-only metadata proposal) and then a Deploy (a real change to your org — only once you approve it). After you sign up, OrgBolt asks how you work with Salesforce: User, Admin / Power User, or Developer.


This only changes how much Salesforce jargon the AI assumes you already know. You can change it later in Settings.
2. Connect a sandbox
The dashboard's Welcome card has two steps, and the second one is locked: the composer stays disabled until an Org is connected. Step 1, Connect your Salesforce org, is where you start.


Click Connect Salesforce org, choose the org to connect, and Salesforce shows its own OAuth consent screen — review the scopes and approve. Once that's done, OrgBolt can read the org's metadata (object and field definitions, Apex, layouts) right away. Record data — the actual rows inside those objects — is a separate, standing consent you grant per Org from Connected orgs in the dashboard; nothing is queried until you turn that on.


3. Describe your first change
Once an Org is connected, Step 2's composer unlocks. Type a one-line request — a safe first one: "Add a Priority picklist field to Account with values High, Medium, Low." Click Create task and OrgBolt opens the task's chat.


4. Read the Work Turn
The task's first Turn is a Work Turn. The AI restates the request, names the target Org, and proposes the simplest solution that fits — here, a Priority__c picklist on Account. It reads the Org's real metadata before proposing anything, then generates the field as a Salesforce metadata Artifact, staged in the task's artifact tray — never pasted XML in chat.


A Work Turn never writes to your org. Read the artifact, ask the AI to change it, or accept it as-is — nothing deploys until you act on the next step.
5. Validate, then Deploy
With an artifact staged, the task's command bar shows a next action — Deploy for a sandbox, Validate first for production. Click it to open the deploy modal: pick Validate (checkOnly) to run every Salesforce validation without committing anything, or Deploy to send the change for real. For a sandbox you can go straight to Deploy — the cost of a mistake there is small.


On failure, OrgBolt shows the error Salesforce returned and offers to go back to Work and retry. On success, it offers the next environment or a mark-done button.
6. Where to go next
- Next time, click Plan in the composer (or type `/planning`) before you build. A Planning session stress-tests blast radius, access, and automation order one question at a time before the AI generates anything — read /help/planning.
- Read /help/deploy for checkOnly validation and the 5-phase metadata ordering.
- Read /help/safety for every non-destructive guarantee OrgBolt makes.

