Choose an admin dashboard for staff who manage the business and a customer portal for customers who need to help themselves. Some products need both. Start by agreeing who can see and change each record, then describe the tasks those people need to finish before deciding which screens to build.
Define roles and permissions
For each role, write down which records the person can see and what they can create, edit, approve, or export. Describe the boundaries in business terms, such as a customer seeing only their own invoices or a staff member managing only their assigned branch. Ask how access changes when someone leaves or changes roles.
A service business that wants to share bookings and invoices with customers might begin with these roles.
| Role | Can view | Can do |
|---|---|---|
| Customer | Their own bookings and invoices | Download their invoices |
| Staff | Bookings and availability for their assigned branch | Manage that branch's schedule and update booking status |
| Manager | Operational reports across branches they manage | Filter reports and export approved summaries |
Write each workflow from start to finish
Pick the routines that justify the project. For each one, describe what starts it, who acts, what changes in the underlying system, and how the user knows it finished. Write down what happens when information is missing or someone changes a record at the same time. This gives a development team a concrete workflow to estimate and test.
Decide where data lives and how users sign in
- Data and integrations: identify the existing systems and which one owns each record. Ask what their APIs can read or update, which tasks need imports or exports, and how discrepancies will be handled. Include backend development in scope if records or access rules need to be managed in a new system.
- Sign-in: consider email and password, single sign-on through a company account, or two-factor login where appropriate. Decide how invitations, password recovery, and account removal should work for each audience.
- Reports and audit history: list the reports people actually use, who can export them, and which changes need a record of who acted and when. Specify the fields users should be able to search or filter, such as booking date, branch, or invoice status.
- Devices and browsers: identify what staff and customers use. Test common tasks on those devices, including invoice downloads on phones and schedule editing on office computers.
Choose an interface that fits the work
If your team already uses Django and trusted staff mainly need to edit records, Django's built-in admin may cover that work. A custom React interface makes sense when staff need guided workflows across several records or customers need their own portal.
Consider Next.js if the project also contains public pages, such as service listings, that need to be discoverable through search. Pre-rendering public content is one reason to choose it. For screens behind sign-in, decide based on the product's architecture and the team's needs.
Worked example: a service business portal
- Customer checks a booking and downloads an invoice
- The customer signs in, opens their bookings, chooses an appointment, and downloads its invoice when the accounting system makes it available. If the invoice is pending, the portal shows its status.
- Staff update the schedule
- A staff member opens their branch calendar, selects a booking, and proposes a new time. The scheduling system confirms availability before saving it, and the customer gets a notice.
- Manager exports a report
- The manager filters completed bookings by branch and date, checks the totals, and downloads an approved summary for the operations meeting.
- Integrations
- The scheduling system owns bookings, the accounting system owns invoices, and an email service sends notifications. The portal shows the last successful sync if fresh data is unavailable.
Use the roles and workflows above as a starting point alongside the project brief checklist. Mark the decisions your team still needs to make.