The Admin Dashboard is the landing page for configuring Bizuno — company info, users and roles, modules, taxes, payment methods, integrations, and system defaults. You set most of it once at go-live and revisit occasionally.

What you can do here #
- Open any admin sub-screen (Company, Users, Modules, Settings).
- See system status widgets — Bizuno version, last backup, active users, failed logins.
- Access the audit log and diagnostic tools.
The sub-menu under Admin #
- Dashboard — this screen.
- Company — your shop’s legal name, address, logo, fiscal year start, default currency.
- Users — who can log in, which role they have, password policy.
- Roles — permission sets (Owner, Manager, Mechanic, Sales Associate, Bookkeeper).
- Modules — enable / disable core and optional modules.
- Settings — locale, tax, shipping, payment methods, form defaults, email config.
- Integrations — third-party connectors (payment gateways, e-commerce, email marketing).
- Audit Log — record of admin-significant actions by user.
Who should have Admin access #
The owner, and one or two trusted operators. A mistake on most admin screens can affect every user and every record in the system. Grant Admin access reluctantly and review the user list quarterly.Important: Never share the default admin account. Create an individual user for every person who needs admin rights and rotate passwords when someone leaves. A shared login is untraceable — the audit log can’t tell you who did what.
System-status widgets #
User avatar → Manage Dashboards → pick Admin, then add:
- Bizuno Version — current version and whether an update is available.
- Last Backup — timestamp and status.
- Active Users — who’s currently logged in.
- Failed Logins (24h) — brute-force indicator.
- Database Size — trending growth.
- Disk Space — especially relevant if attachments are stored locally.
When you’ll visit Admin #
- Day 1 go-live — most of the tabs.
- Hiring / firing — Users.
- Start of a new fiscal year — Company (fiscal year start), Settings (tax rates).
- Turning on a new feature — Modules, Integrations.
- Investigating a problem — Audit Log.
- Keeping up with Bizuno releases — Updates.
The audit log #
Bizuno logs admin-significant actions — user created/deleted, role changed, module enabled/disabled, settings edited, backup run, password reset, failed login. The audit log is searchable by user, date, and action type. It’s not a general transactional log (that’s the transaction history on each record), but it is the place to look when a security or configuration question comes up.
Upgrades #
Bizuno updates (minor bug fixes and occasional feature releases) are managed through your host or admin. Before any upgrade:
- Run a manual backup.
- Read the release notes — look for deprecations or setting changes.
- Apply the upgrade during a low-traffic window.
- Spot-check: open a customer, an item, a report, send a test invoice email.
Tips for Ridgeline Cycles #
- Schedule a quarterly admin review — 30 minutes to go through the user list, the open modules, and the audit log. Many organizations drift here without noticing.
- Document which third-party integrations exist and who manages their accounts (e.g., Stripe). If that person leaves, you need a handover document, not a panic.
- Keep the Admin user count small. Small shops rarely need more than two admins.
Where to go next #
- Company Setup — fill in your shop’s info.
- Users, Roles & Permissions — set up who can do what.
- Modules & Extensions — enable only what you use.