Bizinly Admin

A single Bizinly installation already manages itself — its own team, its own settings, its own permissions (see "The in-app admin area" below). Bizinly Admin is a separate application that sits one level up: the place where the people and installations behind Bizinly are managed, for anyone running more than one.

Why it matters

The moment there is more than one Bizinly installation — one per customer, one per brand, one per region — a few questions stop having a simple answer: who can sign in to which installation, and as what? which modules has this customer actually bought? has anyone actually looked at the audit trail after something goes wrong? how do you bring a brand-new installation online without touching a server by hand?

Bizinly Admin exists to answer all of those from one screen, instead of answering them once per installation and risking a different answer each time.

What it manages

• People — one record per person, with the tenants they belong to, their role in each, and their security status (can they sign in, do they have two-factor sign-in enabled, when did they last sign in). From a person's record: disable their access everywhere at once, send a password-reset link, or reset their two-factor sign-in if they lose their device.
• Tenants — the businesses running on Bizinly: their name, domains, plan, seats and status, and their members with a role each. Suspending a tenant is recorded immediately and switches off its installation.
• Installations and domains — one Bizinly installation can serve more than one business, chosen by the domain it is reached on. A tenant's record lists the installation(s) it owns, the domain(s) that reach each one, and which is primary; adding a domain here is what brings a new installation online, without further server work beyond preparing its data.
• Modules per tenant — which of Bizinly's modules a given business actually has switched on, overriding the platform default for that one tenant only.
• Roles — the role catalogue, edited in place; who holds which role is set from a person's own record.
• Audit — every action taken in Bizinly Admin (a role changed, an account disabled, a tenant suspended) in an append-only log, alongside the underlying sign-in security events.
• Backups — where backups are stored, when the last good one ran, and a way to restore.

Bizinly Admin's own access is itself role-based, with a distinct set of roles (from read-only auditing up to full administration) — separate from any role a person holds inside a particular installation.

The in-app admin area

Inside a single Bizinly installation, its own owner and admin already manage a good deal without ever touching Bizinly Admin: Team members (the owner adds people and sets their role), MCP & connections (the owner's own API keys and assistant connections — see Connect with MCP), Global settings (branding, sign-up rules, e-mail sending, security, file storage), Permissions (what each role may do, screen by screen) and Layout (the menu and the theme). That is local self-service for one business, inside one installation.

Bizinly Admin is the layer above it: the one place that spans every installation, for whoever operates the estate rather than one business within it.

Setting up Bizinly Admin is part of running a Bizinly deployment for more than one customer — book a call if that is what you are building.

Related: Overview & architecture, The starter project, Plugins.