Changing the email address on your Jetstream account used to mean filing a support ticket and waiting for someone to make the change by hand. You can now do it yourself: open your profile, click Edit next to Email, and enter the new address.
Because your email address is how you sign in and how account recovery works, the change is deliberately careful. You confirm it is really you first, using your password, your authenticator app, or a code sent to your current email address. Jetstream then sends a confirmation link to the new address, which is what actually applies the change, so a typo can never lock you out of your own account. Your old address gets a heads-up at the same time with a link to cancel the request, in case the change was not something you asked for.
While a request is outstanding, your profile shows the pending address, when the link expires, and a button to cancel it. Confirming the change signs you out everywhere and disconnects any connected apps, so anything still using the old address has to sign in again. If your team uses single sign-on, your email address is managed by your identity provider and this option points you to your administrator instead.
Writing SOQL by hand meant remembering exact API names, or tabbing back and forth to look them up. The manual query editor and the SOQL panel on the query results page now offer suggestions as you type, pulled live from the org you have selected.
Suggestions follow where your cursor is in the query. After FROM you get queryable objects. In the field list you get that object's fields, along with parent relationships you can keep traversing with a dot and child relationships that expand into a full subquery. After a comparison in a WHERE clause you get values that actually fit the field — picklist entries, true and false, and date literals like LAST_N_DAYS:30. Everywhere else you get the SOQL vocabulary itself: clauses, aggregate and date functions, GROUP BY and ORDER BY modifiers, and scope options.
Salesforce now cuts off an org connection after 30 days without use, and that limit is theirs to enforce, not something Jetstream can extend. Jetstream's own policy was far more generous, which meant your orgs could look perfectly healthy in the app for months after Salesforce had already invalidated the credentials, and the first sign of trouble was a connection that suddenly stopped working.
Expiration dates are now calculated from the last time you actually used the org, plus the 30 days Salesforce allows. Seven days before that date, the org gets a warning badge on its card and in the org dropdown, and a banner appears on the home page. Emails go out at seven days, one day, and on the day itself. Using the org at any point resets the clock, so an org you work in regularly will never warn you.
The desktop app kept your connected orgs in a single file shared by everyone who signed in on that computer. On a shared or virtual desktop, a second person signing in could leave the first person unable to read their own orgs.
Each account now gets its own org storage, so signing in with a different account never disturbs anyone else's connections. Your existing orgs move over automatically the first time you sign in after updating, and nothing needs to be reconnected.
Manage Permissions let you edit what a permission set grants, but changing who it applied to still meant a trip to Salesforce Setup. You can now open a Manage Assignments modal and add or remove users directly.
There are two ways in: the info popover on the permission set list, and a new trigger in the column header above each permission set in the permissions editor. Search for users by name or username, stage your adds and removes, and save them all at once. If Salesforce rejects part of the change, the modal stays open with the error so you can fix it and try again.
Saving edits from query results now has a Save Options section with two controls. Batch size sets how many records go into each API call, up to 200. Serial mode sends those batches one at a time instead of all at once.
These are the same levers Load Records gives you, and they matter for the same reasons. Lowering the batch size helps when records fire heavy automation and hit governor limits, and serial mode avoids the record-locking errors you get when parallel batches touch related records, like several contacts on the same account.
Downloading every record from a query now reports progress using a progress bar with a running count of records retrieved, so you can see how much time is left for the download to complete.
Loading permissions for a set of objects and fields is noticeably faster, especially in orgs with a lot of metadata.
When the SAML signing certificate configured for your team is close to expiring, Jetstream now warns you instead of letting logins break unannounced. Team admins see a banner in the app starting 30 days out, and get email reminders at 30, 14, 7, and 3 days before expiration, plus one on the expiration date itself. Each message links straight to your SSO settings.
Updating the certificate clears the warning, and if the certificate is later replaced with another one that is nearing expiration, the reminders start over.
Permission Analysis produced a lot of useful data that was previously trapped on screen. Every table now has a download button in its header — the object, field, permission set, tab visibility, and user assignment trees, the export grid, the findings modal, and the issues tab. You get the same download options as everywhere else in Jetstream: Excel, CSV, JSON, or straight to Google Drive.
This makes it much easier to hand a specific slice of an analysis to someone else, drop it into a spreadsheet for review, or keep a record of what permissions looked like before a change.
The permission trees used to have separate Expand all and Collapse all buttons. They now use a single toggle that reflects the current state, and the same control has been added to the Field Usage Analysis results, where expanding every object at once previously meant clicking through each group.
Salesforce caps how much data a single bulk batch can contain. Jetstream batches your file by record count, so a load with very wide records — long text areas, rich text, lots of columns — could produce a batch over that cap and fail partway through, even at a modest batch size. Jetstream now checks the size of each batch and splits it further when needed, so these loads run to completion without you having to lower the batch size and retry.
Excel refuses to store more than 32,767 characters in a single cell, but Salesforce long text and rich text fields hold far more than that, and subquery results get written into one cell as well. Downloading records containing those values used to fail with no explanation. Long values are now truncated to fit so the file downloads successfully, and if a download still fails you get a message telling you to use CSV or JSON to get the complete values.
Long-running data loads could fail when your Salesforce session expired mid-job, because the bulk load reports an expired session differently than the rest of the Salesforce API and Jetstream did not recognize it. Jetstream now refreshes your session and carries on, so a load that runs for a while is no longer at the mercy of your session timeout.
If you built a query that selected a very large number of fields — common when you select all fields on a big object, or work with orgs that have hundreds of custom fields — Salesforce could reject it before it ever ran, because the query itself was too long to fit in the request. Jetstream now sends queries in a way that is not subject to that limit, so those queries run like any other.
This applies everywhere Jetstream runs SOQL for you, including the query builder, viewing related records, and the record detail pages.
Jetstream previously made two separate calls to Salesforce for every query — one for your records and one for the column details used to build the results table. Both are now fetched together in a single request, so results show up a little faster.
]]>Manage Permissions now includes a System Permissions tab alongside object permissions, field permissions, and tab visibility. You can review and update system permissions — things like API Enabled or Modify All Data — across all of your selected profiles and permission sets in one table, instead of clicking through each one individually in Setup.
Jetstream also understands how system permissions depend on each other: enabling a permission automatically enables everything it requires, and disabling a permission automatically disables anything that depends on it. This is the same behavior you get in Salesforce Setup, but applied across every profile and permission set you are editing at once.
System permissions are also included when you export your permissions, as a new System Permissions sheet in the Excel workbook or file in the CSV export.
Jetstream now publishes release notes — you're reading them! Each release is documented here on the docs site so you can keep up with new features and fixes as they ship.
]]>The desktop app and browser extension now include the System Permissions tab in Manage Permissions that shipped for the web app in 10.7.0. You can review and update system permissions — things like API Enabled or Modify All Data — across all of your selected profiles and permission sets in one table, with dependent permissions enabled and disabled for you automatically. System permissions are also included in your permission exports.
The web app release includes routine maintenance and security updates, with no changes to how the app works.
]]>Windows desktop users whose automatic updates stopped working after a code-signing certificate change will be back on the normal update track with this release. If your desktop app hasn't been updating, you may need to reinstall it once from the website to pick up future updates automatically.
The desktop app now opens external links and downloads more safely and uses the correct filenames for downloaded files, and the browser extension restricts message handling to trusted sources. These are behind-the-scenes safety improvements with no change to how you use the app.
]]>You can now include comments in your SOQL queries. Jetstream preserves them while you write and edit, and removes them automatically before sending the query to Salesforce — so you can annotate and document complex queries without breaking them.
Bulk record updates now recover better when Salesforce returns an error. Overly large batches are avoided, failures are logged with more troubleshooting context, and you can retry failed records instead of being blocked.
Teams using single sign-on benefit from improved OIDC configuration handling and a more robust discovery process, making SSO setup and sign-in smoother.
]]>Editing records in a table just got a lot more powerful. You can now copy and paste ranges of cells (including to and from a spreadsheet), undo your edits, and preview every change before saving. Inline warnings and errors appear right in the cells, so you can catch problems before they reach Salesforce.
Select a whole range of rows at once: click the first row, then shift-click the last, and everything in between is selected. The last row you toggle acts as the anchor for the next range.
The desktop app and browser extension are updated to the latest release, bringing the recent table-editing improvements — copy, paste, undo, and preview-before-save — to both. This release also includes routine behind-the-scenes maintenance.
]]>When you make a bulk update to records, you can now preview the proposed changes first. The preview lists each impacted record alongside its original and new values, so you can confirm exactly what will change before anything is written back to Salesforce.
Right-click a field's column header in query results and choose to view its metadata. A modal shows the field's details without leaving your results, which is handy when you're deciding how to filter, sort, or update a column.
A round of performance work on the rebuilt data tables makes them feel quicker in day-to-day use. Checkbox (set) filters now evaluate in a single pass instead of once per column, tooltips and popovers render more efficiently, and the initial load of a large result set does less redundant work — so big tables open and respond faster.
Token verification for desktop app and browser-extension sessions is more robust, which reduces unexpected sign-outs and keeps you connected to your orgs.
]]>Teams that sign in with OIDC single sign-on will see fewer failures when their identity provider's discovery endpoint is slow or temporarily unavailable. Sign-in now handles those cases more gracefully and captures clearer diagnostics when something does go wrong, which makes issues faster to track down.
]]>We strengthened how Jetstream fetches identity-provider metadata during OIDC and SAML single sign-on, adding protection against requests being redirected to unintended destinations. There's no change to how sign-on works for you — this is a behind-the-scenes safety improvement for teams using SSO.
]]>We fixed an issue that could crash the data table in certain cases, so query results and other tables render reliably again. This release also includes further reliability improvements for single sign-on.
]]>Jetstream's data tables have been rebuilt on a modern, well-maintained foundation. Beyond keeping the tables healthy for the long run, the rebuild unlocks a much richer way to work with your data wherever Jetstream shows it in a grid:
The rebuild also brings better layout for nested rows and styling that more closely matches Salesforce.
The permission manager now shows a summary of how many permissions are selected for each object. When you're working across several objects at once, that running count makes it much easier to keep track of the scope of your changes before you save them.
The query builder now lets you add WHERE, ORDER BY, and LIMIT clauses to subqueries — not just to
the top-level query. That makes it much easier to shape related-record results without dropping into raw
SOQL.
On pages that move through multiple steps, you can now use cmd+enter to go forward and
cmd+shift+enter to go back, so you can fly through a flow without reaching for the mouse.
Two small fixes make the rebuilt tables feel better to use:
Getting around Jetstream with the keyboard is much smoother in this release. Popovers now properly take focus when they open (previously they often didn't, which made tabbing through them frustrating), and focus returns where you'd expect when they close. The org-info popover and the app tab bar also got keyboard-navigation and focus fixes.
Drag-and-drop for organizing org groups and building query filters feels more reliable and responsive. Moving orgs between groups and rearranging filter rows is smoother as a result.
The web extension's access token was expiring far more often than it should have. That's been fixed, so the extension refreshes its token much less frequently and stays connected more steadily.
This release adds detailed documentation about the Salesforce permissions Jetstream needs, along with a reference to how Jetstream accesses Salesforce data and APIs. It's aimed at administrators who want to grant appropriate, least-privilege access while staying aligned with their security practices.
]]>When a field uses a record lookup and the current value wasn't among the first 50 records returned, the lookup could come up empty. Now it searches for that record individually and populates correctly, falling back to a manual value only when nothing is found. Search terms with single quotes are also escaped properly, so values with apostrophes no longer break the lookup.
When the desktop app can't update itself automatically, it now reports a specific error code and tells you clearly that a manual update is needed, rather than failing silently. The download page also shows the current version for each platform so you can confirm what you're installing.
]]>