Updated
Use case · Admin Panels & Back Offices
Customer admin panel
An internal tool for looking up an account, seeing its history and making the changes support and operations make every day.
What is a customer admin panel?
A customer admin panel is an internal tool that lets support and operations staff look up a customer account, see its plan, usage, invoices and history, and make routine changes safely. It gives non-engineers a controlled way to do what would otherwise mean asking a developer to run a query against the production database.
When it is needed
A product needs one once support requests regularly wait on an engineer: extending a trial, changing a plan, resetting access or issuing a refund. It is also the point at which a company wants a record of who changed what, because changes made directly in the database leave none.
What it includes
- Search across accounts, users and subscriptions
- An account page with plan, usage, invoices and recent activity
- Safe actions: extend a trial, change a plan, reset access, issue a refund
- An audit log of who changed what and when
Before the build
Decisions to make early
Which actions are allowed, and to whom
List the changes staff really make and give each one a permission. A panel that can do anything is a risk; one that can do too little is ignored.
Whether to build it or assemble it
Internal tool builders are quick for simple screens. A custom panel is justified when the actions carry business rules that must match the product exactly.
How actions are recorded
Every change should record the person, the time, the account and the values before and after.
What tends to go wrong
- Letting the panel write to the database directly instead of through the product's own logic, so that the two disagree.
- Giving every member of staff full access because roles were left until later.
- Showing personal data on screens where the task does not need it.
Where it fits
Typically connects to
- PostgreSQL
- Stripe
- Intercom
Teams that use it
- Support
- Operations
Industries
Terms worth knowing
Services involved
FAQ
Customer admin panel: questions and answers
Should we use an internal tool builder or build a custom admin panel?
Use an internal tool builder when the admin panel mostly reads data and performs simple updates, because it will be ready sooner. Build a custom admin panel when its actions must apply the same rules as the product, such as proration on a plan change, or when access control and audit requirements go beyond what the builder offers.
What should a customer admin panel log?
A customer admin panel should log every action that changes data: who performed it, when, on which account, and the values before and after. Read access to sensitive records is worth logging too. The log should be stored where the people it records cannot edit it.
Related use cases
All 40 use casesAdmin Panels & Back Offices
User and role management
Accounts, teams, roles and permissions in one place, with single sign-on for the customers that require it.
Admin Panels & Back Offices
Payments back office
Transactions, payouts, refunds and disputes in one console, with reconciliation against the payment provider.
Admin Panels & Back Offices
Review and approval queue
A queue for the things a person has to check, such as applications, documents or listings, with the decision recorded each time.
Build it. Ship it. Grow it.
Book a free 15-minute call. No sales pitch, just an honest conversation about where you are and what it would take to get where you want to be.
Book a call. It's free15-minute call. No commitment.