Using via Managed Package
Jetstream for Salesforce is available on our Team and Enterprise plans. Learn more about our plans and pricing.
What is Jetstream for Salesforce?
Jetstream for Salesforce is a Managed Package that allows you to access Jetstream features directly within the Salesforce interface. With the Managed Package, you can run queries, view results, and manage your Jetstream data without leaving Salesforce.
When using the Managed Package, none of your Salesforce record data is processed via Jetstream's servers. Instead, the app uses Salesforce's Canvas SDK to make API calls directly from your browser to Salesforce, ensuring that your data remains secure and private.
Jetstream never stores any Salesforce access tokens or data from the Managed Package, and all interactions with Salesforce are handled securely through the Canvas SDK.
Known Limitations
While the Managed Package provides convenient access to Jetstream features within Salesforce, there are some limitations to be aware of:
- Working with multiple orgs at the same time is not currently supported within the Managed Package.
- For deployment features that work with multiple orgs, you will need to download the metadata and then re-upload in the target org.
- Ability to sync query history between different orgs and platforms (we plan on delivering this as an opt-in feature in the future)
Getting Started
Setting up Jetstream for Salesforce takes four steps. The first is done in Jetstream by a team admin, and the rest are done in Salesforce by a Salesforce administrator.
- Authorize your Salesforce org from the Jetstream Team Dashboard.
- Install the package in your Salesforce org.
- Assign the Jetstream permission set to each user who needs access.
- Configure the connected app to pre-authorize those users.
Authorize your Salesforce org
The package only loads in Salesforce orgs that your team has authorized. Until an org is authorized, users who open the app in Salesforce see This org isn't authorized.
A team admin authorizes the org from the Jetstream web app:
- Go to Settings > Team Dashboard and find the Salesforce Managed Package Authorized Orgs card.
- Click Authorize Org.
- Enter your production org id. This is the 15 or 18 character id starting with
00D, found in Salesforce under Setup > Company Information. - Enter your My Domain name, for example
acmeforacme.my.salesforce.com. You can also paste your Salesforce url and Jetstream keeps just the name. - Optionally add a name to help your team recognize the org, then save.
Things to know:
- One production org and all of its sandboxes. Every sandbox that shares the production org's My Domain can use the package, so you only authorize production. If you need to authorize more than one production org, contact support.
- Removing the org turns off access for it and its sandboxes the next time the app is opened. Access also ends if your team's subscription ends.
- Only team admins can add or remove an authorized org.
The card is shown to teams on a plan that includes Jetstream for Salesforce. If you do not see it, contact support.
The people who use Jetstream inside Salesforce do not need a Jetstream account or a seat on your team. They only need access in Salesforce, which you grant in the steps below.
Install the package
Use the links below to install the package, or to upgrade an org that already has an older version installed.
| Version | Released | Install in | Package version id |
|---|---|---|---|
| 1.0.0 (latest) | 2026-11-17 | Production · Sandbox | 04tWj000003YaCDIA0 |
| 0.1.0 | 2026-06-21 | Production · Sandbox | 04tWj000000v9BRIAY |
- Click the Production or Sandbox link for the latest version and log in to the org as a Salesforce administrator. If
your org requires logging in through My Domain, replace
login.salesforce.comortest.salesforce.comin the link with your My Domain, for examplehttps://acme.my.salesforce.com/packaging/installPackage.apexp?p0=.... - Enter the installation password. Reach out to support to obtain the password, and let them know which version you are installing.
- Choose Install for Admins Only. Access for everyone else is granted with the Jetstream permission set in the next step.
- Click Install (or Upgrade) and wait for the installation to finish. Salesforce sends an email when it is complete.
To install with the Salesforce CLI instead, use the package version id from the table:
sf package install --package <package version id> --installation-key <installation password> --target-org <org alias> --wait 10
Upgrading to a newer version keeps your permission set assignments, connected app configuration and each user's preferences.
Assign the Jetstream permission set
Assign the Jetstream permission set to every user who needs access to the app. This grants access to the Jetstream app, tab, page, and related user-preference fields.
You can assign it from Setup > Permission Sets > Jetstream > Manage Assignments.
Configure the connected app
Pre-authorize users to provide the smoothest experience. To do this:
- Navigate to Setup > External Client App Manager in Salesforce
- Find Jetstream for Salesforce in the list and click the name
- Open the Policies tab and click Edit
- Expand the OAuth Policies section and change Permitted Users to Admin approved users are pre-authorized
- Choose a profile or an unmanaged permission set to pre-authorize the users who should have access
When pre-authorizing users, you must choose a profile or an unmanaged permission set. Attempting to use the Jetstream permission set — or any other managed permission set — will result in a save error.
Accessing the App
Open the App Launcher in Salesforce and search for Jetstream, then select it to open the app.
For the best experience, click the Open Fullscreen button to open Jetstream in full-screen mode.
You can also navigate directly to the full-screen page or bookmark it for quick access:
https://{your-domain}.my.salesforce.com/apex/jetstream__JetstreamPage
Limiting Jetstream Tools
By default, every user with the Jetstream permission set can use every Jetstream tool. To give some users a smaller set of tools, such as Query Records without the tools that load data or deploy metadata, assign them the Jetstream: Limited Access custom permission along with a custom permission for each tool and action they should keep.
These custom permissions only change what Jetstream shows. They keep people focused and help prevent mistakes, but they never change anyone's Salesforce permissions, and a determined user can work around them. Everything a user does in Jetstream still runs as their Salesforce user, so use their Salesforce profile and permission sets to prevent them from viewing or changing data.
The custom permissions are included in version 1.0.0 and later. If you do not see them under Custom Permissions when editing a permission set, upgrade Jetstream for Salesforce to the latest version.
How it works
- Users without Jetstream: Limited Access can use every tool and action, even if they also have some of the tool or action custom permissions.
- Users with Jetstream: Limited Access only get the tools and actions whose custom permission they also have. Limited Access on its own shows no tools.
- Tools that are not included are removed from the navigation menu and the home page, and opening one from a link shows This tool is not available to you. Buttons for an action that is not included are hidden, or disabled with a message.
- Tools added to Jetstream in the future stay hidden from Limited Access users until you upgrade the package and grant their custom permission.
- Changes apply the next time the user opens or reloads Jetstream.
- The limits apply when Jetstream is opened from the Jetstream app, tab or page included in the package.
Set up limited access
- In Salesforce, go to Setup > Permission Sets and click New. Give the permission set a name such as Jetstream Analysts and save it.
- Open Custom Permissions and click Edit.
- Add Jetstream: Limited Access, plus the tool and action custom permissions from the tables below that these users should have, then save.
- Click Manage Assignments and assign the permission set to the users. They still need the Jetstream permission set as well.
The packaged Jetstream permission set cannot be edited, so add these custom permissions to your own permission set or permission set group.
Tool custom permissions
Some tools need an action custom permission for their main buttons. Without it, the tool opens with those buttons hidden or disabled.
| Custom permission | API name | Also needs for its main buttons |
|---|---|---|
| Jetstream: Tool - Query Records | Tool_Query | |
| Jetstream: Tool - Load Records | Tool_Load | Create and Update Records, or Delete Records for delete loads |
| Jetstream: Tool - Update Records Without a File | Tool_Update_Records | Create and Update Records |
| Jetstream: Tool - Create New Record | Tool_Create_Record | Create and Update Records |
| Jetstream: Tool - Data History | Tool_Data_History | |
| Jetstream: Tool - Platform Events | Tool_Platform_Events | Create and Update Records to publish events |
| Jetstream: Tool - Automation Control | Tool_Automation_Control | Deploy Metadata and Change Configuration |
| Jetstream: Tool - Manage Permissions | Tool_Manage_Permissions | Deploy Metadata and Change Configuration |
| Jetstream: Tool - Permission Analysis | Tool_Permission_Analysis | |
| Jetstream: Tool - Data Analysis | Tool_Data_Analysis | |
| Jetstream: Tool - Deploy and Compare Metadata | Tool_Deploy_Metadata | Deploy Metadata and Change Configuration to deploy |
| Jetstream: Tool - Create Object and Fields | Tool_Create_Fields | Deploy Metadata and Change Configuration |
| Jetstream: Tool - Record Type Picklist Manager | Tool_Record_Type_Manager | Deploy Metadata and Change Configuration |
| Jetstream: Tool - Formula Evaluator | Tool_Formula_Evaluator | |
| Jetstream: Tool - Export Object Metadata | Tool_Object_Export | |
| Jetstream: Tool - Anonymous Apex | Tool_Anonymous_Apex | Nothing, it can change data and metadata without any action |
| Jetstream: Tool - Apex Test Runner | Tool_Apex_Tests | |
| Jetstream: Tool - Debug Logs | Tool_Debug_Logs | Delete Records to purge logs |
| Jetstream: Tool - Salesforce API | Tool_Salesforce_Api | Nothing, it can send any request without any action |
Action custom permissions
| Custom permission | API name | Covers |
|---|---|---|
| Jetstream: Action - Create and Update Records | Action_Records_Write | Inline and bulk edits in query results, editing and cloning records, insert, update and upsert loads, and publishing platform events |
| Jetstream: Action - Delete Records | Action_Records_Delete | Deleting and undeleting from query results, delete loads, and purging debug logs |
| Jetstream: Action - Deploy Metadata and Change Configuration | Action_Metadata_Deploy | Deploying or deleting metadata, creating objects and fields, toggling automation, saving permission changes and managing permission set assignments |
See Access Profiles for more detail on what each action covers. Anonymous Apex and the Salesforce API tool can make any change the user's Salesforce permissions allow, so leave them out for users who should not make changes.
Troubleshooting
"This org isn't authorized"
The org has not been authorized, or its authorization was removed. Ask a Jetstream team admin to authorize the production org from the Team Dashboard, then reload the app. In a sandbox, confirm that its My Domain starts with the same name as the authorized production org.
"Your browsing session has ended or is invalid"
You may see an error similar to the following when opening the app:
Oops, there was an error rendering Canvas application [Jetstream_Canvas]. Your browsing session has ended or is invalid. Please re-login to Salesforce.com again.
This usually means your current Salesforce session is not compatible with the Managed Package. To resolve it:
- Confirm REST API access is enabled. Make sure the user's profile or permission set has API Enabled (REST API access).
- Make sure you logged in directly to Salesforce. If you opened Salesforce by logging in through another app — for example, by launching it from the Jetstream web app or desktop app — your session may not be valid for the Managed Package.
If the error persists, clear the site data for your Salesforce domain and log in to Salesforce directly:
- Chrome / Edge: While on your Salesforce page, click the icon to the left of the address bar (a lock or tune icon) → Site settings (or Cookies and site data) → Delete data / Clear data, then reload the page and log in again.
- Firefox: Click the lock icon to the left of the address bar → Clear cookies and site data, then reload and log in again.
- Safari: Go to Safari > Settings > Privacy > Manage Website Data, search for your Salesforce domain, remove its data, then reload and log in again.
Alternatively, open a private / incognito window and log in to Salesforce directly — this also resolves the issue.