Four fixes before you contact anyone

The login is in your purchase confirmation email rather than on a public page, which accounts for most of the "I cannot find it" cases. These four steps resolve nearly all the rest.

One: check which email you bought with

If you keep a separate address for purchases, that is the one that works and it is frequently not the one you are trying. This is the most common cause by a distance and it takes five seconds to rule out.

Two: reset rather than remember

The reset link is faster than working through variations and it eliminates the second most common cause in one step. There is no penalty for using it.

Three: check for an older account

Mark Ling has run a launch every September since 2022. Anyone who bought a previous programme may have an existing login and be trying credentials from the wrong year.

Four: try a different browser

Or an incognito window. A stale cached session is behind more failed logins than any platform admits, and switching browser rules it out in seconds.

When to contact support

Once the reset has been tried and failed. Send the payment confirmation with the first message: it skips the whole identity-verification exchange and gets the account restored in one reply instead of four.

If you have not bought yet

No account exists yet, and a surprising number of people land on a login screen while they are still weighing the purchase.

The thing that does exist at this stage is workshop registration: an email address, no card, no obligation. Worth doing while the window is open, because the cart closes 24 September 2026 at 11:59pm Pacific and the sessions run before it.

What support can and cannot do quickly

With a receipt attached, almost anything - resets, address corrections, access restoration. Without one, the same request becomes an identity conversation that takes considerably longer.

So the single most useful thing you can do before contacting anyone is find the payment confirmation. It converts a slow ticket into a fast one.

Why access problems cluster in the first week

Because that is when everyone is logging in for the first time, on a fresh account, from a confirmation email that arrived among launch traffic. Almost none of it is a fault with the platform.

Handling it in the first hour rather than the first month also means any genuine issue gets resolved while the sessions are still running, which is when access actually matters.

Setting it up so this never recurs

Bookmark the member area, save the credentials in a password manager rather than one browser, and keep the confirmation email in a folder you can find. Two minutes on day one and the access question never comes back.

What access includes · Free registration · The replay tracker