FAQ
Frequently asked questions
Everything people ask before they sign up, and most of what they ask afterwards.
Where the AI comes from
Product
No — admins are one of four groups it is built for. Consultants connect as many client orgs as they like, each isolated with its own metadata and context, and document an unfamiliar one in an afternoon. Developers use the Development Studio pair programmer, org-to-org diffs and selective deployments, or drive the same tools from Claude Code and Codex over MCP. Data analysts describe a report or dashboard in plain English, write SOQL in natural language, and edit live records in a spreadsheet view. Architects, RevOps and release managers use it too. One connection, one per-user price, and the same tools underneath for all of them.
No packages and no code. You create a Connected App in Setup (a five-minute, clicks-only task), paste its Consumer Key and Secret into orgadmin.ai, and authorise with OAuth. Your Salesforce password is never entered into orgadmin.ai.
Any edition with API access — Enterprise, Unlimited, Performance, and Developer Editions, plus all sandbox types. Production and sandbox orgs can be connected side by side.
Yes. A workspace can hold as many org connections as you like (production, sandboxes, and client orgs) each isolated with its own metadata, context, and AI learnings.
Turn your workspace into a company workspace and invite your team by email or straight from a Salesforce org. There are owner, admin, member and read-only roles, plus a separate “Deploy & write” toggle per member. Each person connects orgs with their own Salesforce login. Owners and admins see team activity and every deployment and Studio project, and removing someone disconnects every org login they made. Org context and AI-learned knowledge are shared across the workspace; favourites and saved queries stay personal.
Pricing & AI tokens
Security & your data
Yes, when you ask it to — it can deploy metadata, edit permissions, load and edit records, and seed sandboxes. What it never does is change something while you are merely looking around: browsing, chat, search, and analytics run through a client where create, update, delete, and deploy methods do not exist. Every write feature needs the “Deploy & write” permission (owners and admins always have it; members only when an admin grants it), is disabled unless your deployment enables it, and confirmed by you before it runs — with production deploys requiring an explicit per-run confirmation.
OAuth refresh tokens and Connected App secrets are encrypted at rest with AES-256-GCM, never logged, and never sent to the browser. Every Salesforce API call is audit-logged — without tokens.
No. Prompts are sent to the AI provider your workspace admin chooses, under that provider’s API terms, and orgadmin.ai never trains models on your data.
Only briefly, so a dashboard does not re-query your org every time it is opened. The most recent run is kept for the dashboard’s refresh window (15 minutes by default, 24 hours at most), encrypted with AES-256-GCM under its own key, tied to the Salesforce login that read it, and left out of backups. Set a dashboard to Always live and nothing is kept.
orgadmin.ai revokes the token at Salesforce, deletes the stored secrets, and purges all cached metadata and cached dashboard results for that connection.
Salesforce & AI
Security-specific questions live on the security page, and Agentforce comparisons on the comparison page.