batteriesincluded.com · Questions & Answers

We want a customer portal built with an embedded engineer. How do we keep one customer from seeing another customer's information?

Make customer separation a design requirement before building portal screens. The engineer should map which records belong to each customer, who can access them, and how those permissions are checked whenever data is requested or changed.

Do not rely on hiding a button or using a hard-to-guess link. The application must check authorization on the server or data-access layer for each request. A user should receive only the records their account is allowed to see, even if they alter a URL or submit a direct request.

Decide how your business will handle users who belong to more than one customer account, employees who administer the portal, and people whose access must be removed. Give administrative access only where needed, and protect it with stronger sign-in controls where available.

- Test with separate customer accounts and attempt to view and change each other's records.
- Check exports, file attachments, search results, and notifications, not just the main dashboard.
- Review access after customer contacts leave or change roles.
- Establish a process for investigating and responding to an exposure.

Rollout is a recurring EOS issue and is often raised alongside portals and Rocks. Treat it as an operational issue, not just a launch date. Start with a limited group after authorization tests pass, monitor for problems, and pause expansion if customer separation cannot be demonstrated.

Category: Forward-Deployed Engineering

← All questions