Quickstart — first ticket in 10 minutes

Four things happen in this guide: you connect your Salesforce org, install the extension, trigger a harmless test error, and file your first ticket. No packages, no Apex — nothing is installed inside Salesforce.

You'll need: a Salesforce admin login (or a user who can approve a connected app), Chrome, and about ten minutes.

1. Sign up

Open the app and enter your work email — we send a sign-in link (no password to invent). Clicking it creates your organization.

2. Connect your Salesforce org

From onboarding, click Connect Salesforce and approve the OAuth screen. This is a read-only grant for your org's configuration metadata — validation rules, flows, fields — never your records. The consent screen lists exactly two scopes: Manage user data via APIs and Perform requests at any time.

3. Watch the first sync

After connecting you land on the dashboard while we index your org's metadata. Small orgs take under a minute; very large orgs can take a few. You can continue to the next step while it runs.

4. Install the extension

Install the Chrome extension from the store listing your admin was given (or the direct link on the dashboard), then pin it.

5. Paste your extension key

Open Settings → Extension Keys in the app, create a key, copy it, then open the extension's options page and paste it. The options page shows a green check when the key is valid.

6. Trigger a test error

Edit any Opportunity so it violates one of your org's validation rules — most orgs have one on Amount or Stage. No convenient rule? Create a throwaway one:

Test rule recipe (2 minutes): Setup → Object Manager → Opportunity → Validation Rules → New. Rule name Docs_Test_Rule, error condition Amount > 100000, error message "Amount is above the approval threshold." Save, then edit any Opportunity's Amount to 200,000 and press Save. Delete the rule when you're done.

7. See the panel

The moment Salesforce shows the error, the panel appears and diagnoses it. For a validation rule you'll see “We found the cause”, the rule's name as a badge, a plain-English explanation, and a Try this: suggestion.

8. Create a ticket

Click Create ticket, pick a destination under Send to (connect one first if the list says Connect Jira or Linear in Settings — see the destination guides), check What's included, and press Create ticket. You'll get a link — that's a developer-ready ticket with the exact component, your last steps (labels only), and a masked screenshot if you attached one.

That's the loop. Your team hits an error → understands it → the fix request is already in your backlog.

Next steps

• Connect Jira · Connect Linear · Salesforce Cases
• Troubleshooting

Stuck on any step? Email hello@rootcase.io — during the design-partner period a human answers fast.