This guide walks a Salesforce administrator through setting up the Bliro ⭤ Salesforce integration: install the Bliro package once per Salesforce org, connect the org to Bliro in a few clicks and afterwards, every Bliro user in your company connects their own Salesforce account and individually grants access. You never manage user credentials.
Before you start
You are a Salesforce administrator with permission to install packages (
Download AppExchange Packages/Customize Application).Your org has My Domain deployed (all modern orgs do) and supports installed packages and API access (Enterprise, Unlimited, Developer, or Professional with API access).
Each user who will use the integration has the
API Enabledpermission (on their Profile or via a Permission Set).You are also a Bliro admin, signed in at app.bliro.io.
🔒 Setting up Bliro creates and changes nothing in your Salesforce org. Bliro's app settings are managed by Bliro and distributed by Salesforce's standard mechanism for packaged apps. The only value shared with Bliro is a public client ID.
Step 1: Install the Bliro package (Salesforce)
In Bliro, open Settings → Integrations → + → Salesforce → Set up and click Install Bliro in Salesforce. (To install into a sandbox first, use the "Install in a sandbox instead" link.)
Sign in to the Salesforce org where you want to install Bliro, using an administrator account.
On the install screen, choose Install for Admins Only (recommended as regular users never need the setup components) and click Install.
If Salesforce shows Approve Third-Party Access, tick Yes, grant access to these third-party web sites and click Continue.
Wait for Installation Complete. You can verify the install under Setup → Installed Packages → Bliro.
Step 2: Connect your org to Bliro
In Salesforce, open the App Launcher (grid icon), search for Bliro Setup, and open it. The page shows that your org is ready, together with the app's public client ID and your org's domain.
Click Finish setup in Bliro. Bliro opens, registers your Salesforce org automatically in the background, shows a confirmation, and takes you straight to the Salesforce integration page.
That's the entire org-level setup. About 3 minutes in total.
Step 3: Connect your own Salesforce account
On the Salesforce integration page you just landed on, click Connect. Make sure your browser is not blocking pop-ups.
Sign in to Salesforce if prompted, review the requested permissions on the Allow Access screen, and click Allow.
You are returned to Bliro with the integration showing as Connected.
Step 4: Your team connects (self-service)
Each Bliro user opens Bliro → Settings → Integrations → Salesforce → Connect, signs in to Salesforce, and approves the consent screen. From then on Bliro acts strictly as that user, respecting their Profile, Permission Sets, sharing rules, and field-level security. Users who have not consented cannot be acted for.
Staying in control (admin reference)
In Salesforce (Setup → External Client App Manager → Bliro → Policies): update permitted users to approved profiles/permission sets, manage the refresh token lifetime, or disable the app with one click. It's also possible to revoke a single user under Connected Apps OAuth Usage.
In Bliro (integration page → ⋮ menu): set the instance as the organization default, or delete the integration for the whole organization (disconnects every member).
Uninstalling the package (Salesforce → Setup → Installed Packages) invalidates all tokens immediately.
Troubleshooting
Problem | What to do |
| Salesforce distributes the app's configuration with a short delay after installation. Wait a few minutes and try again. If it persists, confirm the package is installed in the same org you are signing in to. |
The Bliro Setup page says the app was not found | The package is not installed in this org yet — complete Step 1, then reload the page. |
A team member's Connect button is disabled | The org setup (Step 2) has not been completed yet, or the user is not permitted by the app's Permitted Users policy in Salesforce. |
The Salesforce pop-up does not appear | Allow pop-ups for |
"Insufficient privileges" during install | Your Salesforce user cannot install packages. Ask a Salesforce administrator to complete Step 1. |
Connected, but Bliro cannot read or write a record | Bliro acts as the signed-in user. Check that user's Profile, Permission Sets, and Field-Level Security allow the action in Salesforce. |
Security & permissions
Zero footprint: nothing is created or changed in your Salesforce org; the setup page is read-only.
No secrets: Bliro authenticates with the OAuth 2.0 authorization-code flow with PKCE (required). A consumer secret does not exist anywhere in the flow. Refresh tokens rotate on every use and expire when idle.
Per-user consent: every user approves access individually on the standard Salesforce screen; Bliro is always bounded by that user's permissions.
For the full authentication model and requested OAuth scopes, see Salesforce Integration: Setup and Security Overview.
Need help?
If you get stuck during installation or connection, contact [email protected].