Putting Salesforce in the Dock, out of the browser

Salesforce is where the whole day happens, and on a Mac it has no home. It is a tab, usually several tabs, usually mixed in with a spreadsheet, a mail client and whatever else the browser is holding. Searching for a Salesforce desktop app returns the free CRM signup, the mobile app listing, and a community thread asking the same question. None of it is an installer for macOS.

The short answer is that no such installer exists. The longer answer is that a window in the Dock is available anyway, that it solves some of what people are actually complaining about, and that it pointedly does not solve one of the big ones.

What Salesforce ships for a desktop, and what it does not

A search of the Mac App Store for software published by Salesforce returns nothing. There is no native Mac client for the CRM, and there has not been one to find.

The mobile app does not provide a back door either. Its App Store listing states compatibility with iPhone requiring iOS 18.0 or later, iPad, and Apple Vision. Absent is the Mac line that appears on listings where a developer has allowed the iPad build to run on Apple silicon, so installing the Salesforce mobile app on a Mac is not an option the way it is for a handful of other business tools.

It is not only an Apple situation. A search of the Microsoft Store for software published by salesforce.com turns up Salesforce Chatter rather than a CRM client, so the missing desktop application is missing on both desktop platforms. Salesforce's own help site also marks the page for setting up Salesforce for Outlook on the desktop as retiring, which is a reasonable summary of the direction: the product lives in the browser, and integrations point at mail rather than at a desktop client.

That settles what the client is. The org's own Lightning domain in a browser is the Salesforce application, and the question is what kind of window it opens in.

Three different requests hide behind the same search

"Salesforce desktop app" is typed by people who want three unrelated things, and the routes below only answer two of them. Sorting out which one applies saves a lot of wasted effort.

The first request is a window. Salesforce deserves to be an icon rather than a tab, reachable with one gesture, out of the pile where the rest of the browser lives. This is the common case and it has a good answer.

The second request is fewer interruptions: notifications that arrive on the desk rather than inside a tab that is not visible, and a session that survives the working day. Half of that is solvable and half is not, which the next two sections cover.

The third request is offline access, and it is worth stating plainly that no browser based route provides it. Every option here is a window onto a live website, so a train with no signal means a blank window, exactly as it would mean a blank tab. Anyone whose real requirement is working through records without a connection should evaluate what the mobile apps offer for that rather than rearranging how the desktop opens.

Being clear about which of the three applies also decides how much effort is worth spending. The first takes two minutes. The second is a conversation with an administrator. The third is a different product question entirely.

The routes, side by side

Route	Setup	Sign in state	Notifications	Fits
Browser tab	Nothing to do	Shares the browser session	Browser permission, browser must be running	One org, light use
Safari, Add to Dock	Two clicks, macOS Sonoma 14 or later	Its own cookie store, separate from Safari	System notifications, unread badge	One org, kept out of the browser
Chrome, Install page as app	Two clicks in Chrome	Inherits the Chrome profile it was made from	Through Chrome, which must be running	Anyone relying on browser extensions for admin work
Site to app tool	A few minutes, one app per org	Its own store per app	System notifications per app	Several orgs, sandboxes, client work

Apple added the Safari route in macOS Sonoma 14 and documents the property that makes it more than a bookmark.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. In this way, it keeps your browsing separate, similar to using a Safari profile. Source: support.apple.com

The steps are File then Add to Dock from the Safari menu bar, or the Share button then Add to Dock. Chrome's version lives in the three dot menu under Cast, save, and share, then Install page as app, and yields a window tied to the Chrome profile it was built from.

The thing a window will not fix

It is worth being blunt about this, because it is the most common reason people go looking for a desktop app in the first place. Being logged out of Salesforce is not a browser problem, and putting Salesforce in its own window does not extend a session by a minute.

Session length is an org setting, controlled by an administrator in Setup rather than by whatever is displaying the page.

Use the Session Settings screen to configure session security. You can configure settings such as the session connection type, timeout restrictions, and IP address ranges to protect against malicious attacks. Source: help.salesforce.com

Two settings on that screen account for most complaints. Timeout restrictions decide how long an idle session survives, and they are deliberately short in many orgs. The other is the option to lock sessions to the IP address they originated from, which is available in several editions and which will end a session the moment the network address changes. Anyone who moves between a desk, a meeting room and a VPN in one afternoon will be signed out repeatedly, and no container changes that.

Naming the real cause is useful because it points at the real fix, which is a conversation with whoever administers the org rather than an hour spent looking for software. What a separate window does change is the aftermath: signing back in happens inside one application that then returns to the same record, instead of across three scattered tabs that each need attention.

What the window does change

Salesforce becomes an application. It sits in the Dock, answers to Command and Tab, and can be found in Spotlight under whatever name it was given. The difference is largest for people who keep a browser full of other work, because the CRM stops competing for tab position with everything else.

It can be pinned and it can start itself. The Dock icon can be assigned to a specific desktop space through its Options menu, and Apple documents that a web app can be added as a login item so that it opens at sign in. A window that is already open and already at the right screen removes a small friction that happens dozens of times a day.

The chrome disappears. Apple describes the web app toolbar as a streamlined one with back and forward buttons and the Share button, and its settings pane allows the name, URL and icon to be changed later, or the navigation controls to be hidden entirely. Salesforce already draws its own navigation bar, and removing a second one above it returns a strip of vertical space on every screen. Console style apps keep their own tabs inside the page, so a single window is rarely a constraint.

Notifications become system notifications, with one condition that Apple states directly.

Web apps support an additional notifications feature: The number of unread notifications appears as a red badge on the app's icon in the Dock. To use this feature, respond to the website's notifications request in the web app, not in Safari. Source: support.apple.com

The permission has to be answered inside the new window, because nothing is inherited from the browser. Once it is, the app appears in System Settings under Notifications by name rather than by URL, and Focus modes apply to it like any other application.

Several orgs, and the reason this matters more here than elsewhere

Most people who use Salesforce seriously touch more than one org. A production org and a sandbox. An employer's org and a client's. An admin or consultant with five. Each org answers at its own domain, and the sandbox login at test.salesforce.com is a separate door from the production one, so the tab strip fills up quickly and the tabs look identical.

Two problems follow. The first is navigational: finding the right tab among several that render the same interface with the same favicon. The second is more serious, which is editing a record in production while believing it is the sandbox. No warning banner prevents that reliably once the tabs look alike.

Separate windows with separate storage address both. Each app can carry its own name and its own icon, so the Dock itself says which org is which, and each window holds one session that cannot be confused with another. Apple's route covers the first split between the browser and one app. Past that, a tool that turns a website into a standalone Mac app is the practical answer, because it builds one app per org with its own store and its own icon rather than relying on the browser to keep them apart. That arrangement is described on the Features page, and the presets already prepared for common services are listed under Supported services.

The rough edges to expect

Identity verification on the first launch. The new window carries none of the browser's cookies, so Salesforce sees a browser it does not recognise and will ask to verify identity with a code before letting the session start. That happens once per app, and it is the isolation working as intended.

Browser extensions stay in the browser. Admins and developers who lean on inspector style extensions should note where those live. An extension installed in Chrome is available to an app built from Chrome, and a Safari extension appears in the toolbar of a Safari web app, since Apple documents extension buttons as part of that toolbar. Building the window from the wrong browser quietly removes a daily tool.

Links leave the window. A record that links out to a document, a form or an external system opens outside the app. That is correct behaviour, and the Share button offers Open in Safari for anything that genuinely needs the full browser.

Chrome built apps depend on Chrome. Quitting the browser closes them. If the point was to finish the day by quitting the browser, the Safari route or a standalone tool matches the intention better.

What to change first

Open the org in Safari, use File then Add to Dock, name the app after the org rather than after Salesforce, and allow notifications from inside the new window. If the recurring pain is being signed out, take that to the administrator and look at the session timeout and the IP locking setting, because no window changes those. If the pain is five orgs that all look the same in a tab strip, build one app per org with Kagemusha and give each one an icon that is impossible to mistake.