All topics

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.

The post-signup experience picker, offering User, Admin / Power User, and Developer as options.
The post-signup experience picker, offering User, Admin / Power User, and Developer as options.
Pick the option closest to your day job — later Turns tailor their explanations to it.

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.

The Welcome card before any org is connected: Step 1 reads Connect your Salesforce org, and Step 2, Describe your change, is greyed out with the composer disabled.
The Welcome card before any org is connected: Step 1 reads Connect your Salesforce org, and Step 2, Describe your change, is greyed out with the composer disabled.
Step 2's composer stays locked until Step 1 is done — there's nothing to describe a change against yet.

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.

The Welcome card after an org is connected: Step 1 reads Connect your Salesforce org with a green Connected label, and Step 2's composer is unlocked with the connected org named beside it.
The Welcome card after an org is connected: Step 1 reads Connect your Salesforce org with a green Connected label, and Step 2's composer is unlocked with the connected org named beside it.
Step 1 is checked off and Step 2's composer unlocks — you're ready to describe a change.
Start with a sandbox. OrgBolt is non-destructive by default — Work is read-only and Deploy offers Validate-first for production — but the fastest way to build trust in any new tool is to watch it work in a sandbox first.
If login fails immediately with "An unexpected error has occurred during authentication" and no consent screen — Salesforce's error code for this is OAUTH_APPROVAL_ERROR_GENERIC — your Salesforce user is missing the "Approve Uninstalled Connected Apps" permission — Salesforce has required it since September 2025 for any connected app not yet installed in the org. Ask an admin to grant that permission, or install OrgBolt first via Setup → Connected Apps OAuth Usage → Install (retry after the first failed attempt), then reconnect. In a sandbox where the permission doesn't appear in the profile/permission-set editor at all, run Setup → Company Information → Match Production Licenses first.

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.

A task's opening chat message: "Add a Priority picklist field to Account with values High, Medium, Low."
A task's opening chat message: "Add a Priority picklist field to Account with values High, Medium, Low."
Plain English in, no SFDX, no XML, no packaging to think about yet.

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.

The task's staged artifact block, showing the generated Priority__c picklist field with its High, Medium, Low values.
The task's staged artifact block, showing the generated Priority__c picklist field with its High, Medium, Low values.
The artifact tray: what Deploy will send to your org, visible before anything touches Salesforce.

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.

A system event in the task chat reporting a successful deploy to the connected Salesforce org, with the deploy ID.
A system event in the task chat reporting a successful deploy to the connected Salesforce org, with the deploy ID.
A real deploy result — the Salesforce deploy ID is there to look up in Setup → Deployment Status.

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.
The Help index, listing every topic as a card with its title and one-line summary.
The Help index, listing every topic as a card with its title and one-line summary.
Every topic in one place — the Help index (Settings → Help).