Choose the customer actions
Decide whether the portal lets a customer view a saved selection, request an alternative, inspect a proposal or provide missing information. Distinguish those actions from unrestricted changes to an accepted order. A branded login alone does not establish the permissions or workflow the customer needs.
Preserve record ownership
Create a small action table for the proposed portal: view a saved design, read an issued quote, upload requested site material or ask for a change. For each action, name the source record and the internal recipient. A customer-requested change should reach sales as a request linked to the accepted version. Specify portal functions directly in the software brief; a broader website project does not establish which portal actions are included.
Test access and revisions
Verify access to the correct customer's project and the document version shown. Test revoked access, a revised proposal and an accepted-order change. Decide which information is internal only and how customer questions reach the assigned team before making the portal operational.
Implementation checklist
- Customer actions defined
- Authoritative records
- Role and project access
- Revised document visibility