Client sites you maintain

A stolen admin cookie needs no password to reach the checkout settings. Twenty client panels are twenty admin logins, and one browser holding all of them means one theft reaches all of them.

There is no platform here to link your clients, because the sites belong to them. The admin session is the account: it gets stolen, and a security plugin watches it.

A profile is a browser of its own. It has its own folder, and everything the engine saves goes there: cookies, storage, saved sign-ins and history.

Nothing crosses between two such folders, because the engine does not know the neighbour exists. The rule that follows is boring: one client, one profile, even when two sites sit on the same hosting.

The pair that opens a panel lives on the profile that uses it, with the sign-in page and a note for the half sentence that has nowhere else to go.

The system seals the password on Windows only: on macOS the key ships inside the program, and on Linux it is written as typed. It never reaches our server.

• Login and password

  On the profile, and on the built in engine one press puts them into the open form.

• Sign-in page

  The address of that panel, saved as a note rather than as a shortcut that opens it.

• Second step

  The key produces the six digits on this machine, with no network call and no phone.

• A table you already keep

  The spreadsheet import recognises a column of keys by its name, in English and in Russian alike.

Security plugins watch where an administrator signs in from, and an address the site has never seen brings a second check or a lockout.

A profile pinned to one exit address makes those sessions look like the same person at the same desk, which is what they are. Clock and languages follow the exit country for the countries in the app's own list.

Editing products through a panel at machine speed is read as a compromised account rather than a busy maintainer. The plugin does not ask who you are before it locks the panel for an hour.

These numbers are shown on the profile card as guidance, and the app itself counts only page loads in the profile window. It does not stop you.

You share the profile, not the password: Share with the team in the profile menu. It appears in their list marked shared with you, and the settings and the fingerprint as generated travel with it.

Taking it back is one untick, and the profile leaves their app on the next sync. Group access narrows a contractor to the clients they work on.

• One window per profile, takeover by consent

  Signed in and with the server reachable, a start claims it for three minutes and renews every minute.

• A refusal names the holder

  The second machine is told which machine holds the profile and since when.

• The log outlives the person

  Every row carries the workspace it happened in, so a departure does not empty your history.

Every scenario loads the general tracker list, and it closes crash collectors, performance monitors and session recorders along with the analytics.

There is no switch for it on a profile, so a recorder a client pays for will not see a session run inside one. To check that an error reached its collector, open that page in your everyday browser.

• Crash reports

  sentry.io and bugsnag.com

• Performance

  newrelic.com

• Session recording

  logrocket.com, hotjar.com, fullstory.com and mouseflow.com