Customer Portals: What to Include in Your First Release
A customer portal's first release should let customers do the two or three things they most often phone or email you about, and do them securely. For most businesses that means logging in and recovering access, seeing the status of their orders, projects or requests, downloading their documents, sending a request linked to their account and keeping their contact details current – plus an admin side for your staff. Strict access control, so that each customer sees only their own data, belongs in the first release, not a later one. Live chat, native mobile apps, dashboards and extra integrations can usually wait.
Start from what customers ask you
Before listing features, go through recent customer emails and calls and sort them by type: "where is my order?", "can you resend the invoice?", "please change the delivery address", "what is happening with my request?". The most frequent types define the first release. A portal that answers them gives customers a reason to log in; a portal full of features nobody asked for gets ignored.
Then decide where the data comes from. A portal is usually a window into data that already exists – in an order system, accounting software or a CRM. Choose one system of record for each kind of data and decide whether the portal reads it in real time through an API or through regular synchronisation. If a mobile app may follow, design the API so both can use it; see one API for a website and a mobile app.
What belongs in the first release
1. Login that is secure and easy to use
- Invitation or open registration. Accounts created by your staff, with an invitation sent to the customer, are easier to control. Open registration needs a safe way to link a new account to an existing customer record.
- Sensible password rules. NIST's digital identity guidelines (SP 800-63B-4, published in final form in July 2025) require passwords used as the only factor to be at least 15 characters long, or at least 8 when they are part of multi-factor authentication. They rule out other composition rules, such as mandatory mixtures of character types, say users must not be forced to change passwords periodically, and require new passwords to be checked against a blocklist of common or compromised ones.
- Password managers and paste allowed. NIST says verifiers "SHALL allow the use of password managers and autofill functionality". Under WCAG 2.2 success criterion 3.3.8 (level AA), blocking password managers or paste is an accessibility failure unless another method is offered.
- Limits on failed attempts. NIST also requires rate limiting of failed login attempts.
- Two-factor authentication as an option, or as a requirement if the portal shows sensitive data such as contracts or financial details.
2. Password reset done properly
OWASP's Forgot Password cheat sheet lists the essentials: return the same message whether or not an account exists, make reset links single-use and time-limited, do not log the user in automatically after the reset, email the user that the password has changed, and offer to end their other sessions. Without self-service reset, every forgotten password becomes a support request.
3. Each customer sees only their own data
This has to be right on day one. Broken access control is number one in the OWASP Top 10:2025, and OWASP reports that 100% of the applications tested had some form of it. One example on OWASP's list is "viewing or editing someone else's account by providing its unique identifier" – in a portal, changing the invoice number in the address bar and seeing another customer's invoice. OWASP's advice includes denying access by default and enforcing record ownership in server-side code, where users cannot tamper with the checks.
Plan roles from the start, even if there are only two at first: for a company customer, an administrator who can invite colleagues, and regular users; for your staff, rules about who sees which customers.
4. Status of orders, projects or requests
A list of the customer's current items with a clear status and the date of the last change answers the most common question without a phone call. Use the status names your staff use, explained in plain words.
5. Documents
Invoices, contracts, certificates, delivery notes, manuals – whatever customers now ask you to resend. Documents must pass the same access checks as everything else; a download link that works for anyone who has it bypasses the login.
6. Requests and messages
A form for new requests, linked to the customer's account and to the specific order or project, with attachments. Staff see it in the admin; the customer sees the reply in the portal and gets an email.
7. Profile and personal data
Let users update their contact details and notification preferences. The portal also helps with GDPR: the European Data Protection Board's guide for small businesses says organisations must facilitate the exercise of data subject rights, "in particular via electronic means", and answer requests within one month. Access, correction and data portability – receiving data in "a structured, commonly used and machine-readable format" – are easier to handle when the data is already organised per customer.
8. The admin side
- creating and deactivating customer accounts and users;
- seeing what a customer sees, to answer their questions;
- a log of important actions such as logins, downloads and changes;
- simple management of statuses, documents and requests.
9. Email notifications
One email for each event that matters to the customer – status changed, document available, request answered – with a link to the portal. Nothing more in the first release.
10. Works on a phone and with assistive technology
Many customers will open the portal from an email on their phone. Forms, tables and downloads must work on a small screen and with a keyboard. See our accessibility checks for forms and navigation.
What can usually wait
| Feature | Why it can wait | Simpler first step |
|---|---|---|
| Live chat | Needs staff available at set hours | Request form with email notifications |
| Native mobile app | A second product to build and publish | A portal that works well in the phone's browser |
| Dashboards and charts | Useful once you know what customers look at | Lists with filters and an Excel export |
| Online payments | Needs a payment provider and reconciliation | Invoices in the portal with bank details |
| Integrations with several systems | Each one adds work and risk | One system of record at first |
| Several languages | Every text and email must be translated and maintained | The language most customers use |
Any of these belongs in the first release if it is the main reason customers contact you. If most calls are about payments, online payment comes first.
Launch with a small group
Invite a few customers first, ideally ones who contact you often and will tell you honestly what does not work. Watch what they use, what they still call about and where they get stuck, and plan the second release from that rather than from the original wish list.
We build customer portals as part of our web-based software work: login and roles, the admin side, and the connection to the systems where your data already lives. Send us the questions customers ask you most often and a list of the systems you use today, and we will propose a first release built around them. Contact us.
Sources
- A01:2025 Broken Access Control – OWASP Top 10:2025
- Digital Identity Guidelines: Authentication and Authenticator Management (SP 800-63B-4) – NIST
- Understanding Success Criterion 3.3.8: Accessible Authentication (Minimum) – W3C WAI
- Forgot Password Cheat Sheet – OWASP Cheat Sheet Series
- Respect individuals' rights – European Data Protection Board (Data protection guide for small business)