Kajabi for desktop on a Mac: your courses in one window

The work happens on the computer. Course videos get uploaded from the computer, email campaigns get written on the computer, checkout pages get built on the computer, and the sales numbers get read on the computer. So searching for Kajabi for desktop is a reasonable thing to do, and finding that every Kajabi application is a phone application is a reasonable thing to be annoyed by. The gap is real, and there is a practical answer to it that has nothing to do with waiting for a download link.

What Kajabi actually publishes as an application

Kajabi maintains four applications, and all four are mobile. The App Store listing for the main one is unambiguous: Kajabi, published by Kajabi, LLC, free, 51.1 MB, Business category, and a compatibility line reading "Requires iOS 16.6 or later." The devices named above the description are iPhone and iPad. There is no Mac entry, which means the iPad build has not been allowed to run on Apple silicon either, and searching the Mac App Store for anything published by Kajabi, LLC returns nothing.

Application	Platform	Who it is for
Kajabi Mobile App	iOS, Android	Members consuming content
Branded Mobile App	iOS, Android	Members, under the creator's own brand
Kajabi Creator	iOS, Android	Recording and uploading on the move
Kajabi Cofounder	iOS	Drafting with the AI assistant

Notice what is missing from that table: the dashboard. Kajabi's own documentation describes the Kajabi Mobile App as giving customers access to courses, coaching, private podcasts and Backstage, with a magic-link login or a six digit code. Administrators can sign in to manage a community, but building products, editing pages, sending campaigns and reading analytics are not what these applications do. They are the member experience, not the creator's workbench.

The Branded Mobile App is the same category of thing with the creator's name on it, listed at $199 a month as an add-on and included in the Pro plan. Useful, and still a member app.

The dashboard is the product, and the dashboard is a browser

Everything a creator actually does with Kajabi happens on a web page: Products, Website, Funnels, Email Campaigns, Contacts, Analytics, Kajabi Payments, the Universal Inbox. There is no desktop client, and Kajabi does not claim one. On a Mac, the browser is the application.

That is not a problem in itself. It becomes a problem because of what kind of browser session it is. A Kajabi dashboard is a long session with real stakes: a video upload that takes twenty minutes, an email to a list of eight thousand people, a checkout page connected to live payments. Those things are being done in a tab, in a browser that also holds thirty other tabs, a stack of extensions and years of accumulated site data.

The supported services list shows how many tools end up in exactly this position, where the web version is the only version and the only thing worth improving is the container.

Two jobs, one tab strip

There is a second reason the tab is a bad fit, and it is about roles rather than reliability. A creator on Kajabi is both the administrator and, frequently, a member of their own site, checking what a lesson looks like from the customer side. Those are two different logins on the same host. A browser profile holds one session per site, so checking the member view means signing out of the dashboard or opening a private window that forgets everything on close.

Admin seats make this concrete. Kajabi's plan comparison lists 2 admin users on Basic, 11 on Growth and 26 on Pro. Any team large enough to use those seats is a team where several people are signing in and out of the same host from the same machines.

The failure Kajabi documents itself

Kajabi's own support documentation for customers who cannot log in lists browser causes before anything else, and the third item on that list is specific.

If switching browsers and clearing cache didn't help, the issue may be caused by an ad blocker, privacy extension, or the browser's tracking-protection settings blocking Kajabi's authentication cookies. Source: help.kajabi.com

The recommended test is to open the login page in an incognito or private window. That works because it produces a session with no extensions interfering and no old cookies in the way, which is a description of what a clean window is.

Read that advice as a specification rather than a workaround. The environment Kajabi needs is a current browser, authentication cookies allowed to persist, and nothing blocking them. A main browser configured for privacy while reading the news is not that environment, and it is where most people run their business.

The same article notes that a customer's login is case-sensitive against the email in the Contacts tab, and that a manual Change Password option exists when reset emails will not arrive. Those are worth knowing when a customer writes in, and neither is fixed by a window. What the window fixes is the cookie problem, which is the one that recurs.

Two-factor authentication and a session that keeps resetting

Kajabi supports two-factor authentication, and its documentation states an important limit: it is available to Kajabi account owners and account users, and not to the customers of websites powered by Kajabi. So the account with access to payments, contact lists and email sending is the one that can be protected, and it should be. The setup path runs from the Dashboard through Account settings to Sign In and Security, enabling it logs the session out and back in, and the two methods offered are an authenticator app or SMS.

The reason this interacts with the container is that admin sign-in is a separate login from the member sign-in, on a separate address.

Account users log in at the Kajabi login page. They are managed under Settings > Manage Users, not under Contacts. Source: help.kajabi.com

Two logins on two addresses, one for the team and one for customers, is precisely the situation a single browser profile handles worst. It is also why the same documentation recommends adding team members as account users rather than sharing one set of credentials, so nobody is passing two-factor codes around.

The practical consequence on a Mac is friction. Two-factor authentication is fine when the session persists and a code is needed occasionally. It becomes a daily tax when the browser clears cookies on quit, or when a privacy extension drops the authentication cookie, because then every visit is a fresh login and a fresh code. A window that keeps its own session store, independent of whatever the everyday browser is configured to forget, turns a daily code into a monthly one.

Giving the dashboard its own window

macOS has a documented route for this that costs nothing, and Apple is precise about what it makes.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

The path in Safari is File then Add to Dock. Apple's article, which requires macOS Sonoma 14 or later, states that the result is saved to the Applications folder of the home folder, so it appears in Spotlight, keeps a fixed Dock position and answers to Cmd+Tab. Inside the window, a settings panel allows the name, the icon and the URL to be changed, can hide the navigation controls so it stops looking like a browser, and carries an Extensions tab where Safari extensions can be enabled or disabled for that window alone.

That Extensions tab is the setting that matters most here. Switching off a content blocker for the Kajabi window, and nowhere else, is the exact remedy Kajabi's own troubleshooting article describes, applied permanently instead of once in a private window.

Setting the Application URL to the Dashboard rather than the marketing site is the other change worth making immediately, since it removes a redirect and a click from every launch.

Where the built-in route runs out is session control. A Safari web app uses Safari's engine and its own store, which handles one login well. A site to app tool covers what comes after that: a window holding a session entirely of its own, a second window for a second login on the same host, and a choice about what each window is allowed to do. A dashboard and a member view are two such windows, and so are two brands.

What to test in the first ten minutes

Three checks settle whether the window is doing its job. Whether the login and the two-factor code survive a full restart of the Mac, because that is the whole point. Whether a large video upload completes without the window being backgrounded into trouble. And whether file downloads, particularly a contacts export, land in the expected folder rather than disappearing.

Two brands means two windows, not two browsers

Kajabi's plan comparison lists 1 website on Basic and Growth and 3 websites on Pro, and anyone on Pro with three sites is running three brands from one account. Agencies and consultants go further and hold logins to several clients' Kajabi accounts.

A browser handles that badly. One session per host means signing out of one brand to reach another, or scattering logins across different browsers and remembering which is which. The failure that follows is not theoretical: sending a campaign from the wrong brand is a mistake that cannot be recalled, and it happens when two identical-looking tabs are one click apart.

Separate windows, each with its own session and its own icon, make the Dock the switcher. Two names and two icons are much harder to confuse than two tabs with truncated titles, and the number of windows a setup allows is worth checking before committing.

What a window does not change

It is worth being clear about the limits, because no container changes the account. Kajabi's plan prices as listed today are $143 a month on Basic when billed annually against $179 monthly, $199 against $249 on Growth, and $399 against $499 on Pro. Contact limits run 2,500, 25,000 and 100,000, with extra contacts sold in blocks of 25,000 for $125 a month. Kajabi Payments processing runs 2.9% plus $0.30 on Basic, 2.8% on Growth and 2.7% on Pro, and using a third party provider instead adds 2%, 1% or 0.5% depending on plan.

Those numbers are set by the plan, not by how the dashboard is opened. What a window changes is the number of times a day the session breaks, the number of two-factor codes typed, and the odds of closing a half-written campaign by reflex. For work that runs on deadlines, that is the part worth fixing this week.

What to change first

Put the Kajabi Dashboard into a window of its own, set that window's URL to the Dashboard rather than the marketing site, and disable the content blocker for that window only, which is the fix Kajabi's own support article points to. If a second window is needed for the member view or a second brand, Kagemusha is one way to get it.