Frequently asked questions

Read access, and nothing else. You create an External Client App in your own org and authorise it; there is no managed package. SF2BI only issues SELECT queries. Because Salesforce’s api scope does not distinguish reading from writing, connect it as a user with a read-only profile and Salesforce enforces that for you. The full list of objects is on the Privacy & security page.

No. There are no queries for Accounts, Contacts, Leads, Opportunities or Orders, and none for files. It reads configuration — who holds which licence, who has admin rights, who logged in, what Salesforce invoiced you. Your staff appear in those reports by necessity, and their names and addresses are partially masked on screen and in exports.

About ten minutes, once. Create the External Client App, choose the user it runs as, then paste its Consumer Key and Secret and authorise. The wizard walks the exact Setup screens.

They are list price until you tell us your rates, and list overstates — enterprise contracts commonly run well under it. Upload an invoice and every figure is recalculated at what you actually pay.

Because Salesforce does not expose the rates anywhere else. The API returns invoice headers — number, date, total — with no line detail, so the per-seat rate and the add-ons riding each seat exist only in the PDF.

Yes — production, UAT and sandboxes. Each is a separate read-only connection and you switch between them from the header.

Only AI work: copilot answers and invoice extraction, charged at what each one actually cost to produce. Viewing dashboards, running reports, the advisors, exports, connecting orgs and settings are free.

Yes. The workspace owner invites teammates by email. Everyone shares the Salesforce connections, the data and the token balance; each person’s copilot chat history stays private to them.