Map internal events to approved customer-safe milestones and explanations.
Customer and service / Customer portal and documents
Solar customer portal and document workflow
Give customers a clear view of what has happened, what is needed from them, and which approved documents belong to their project.
Record
01Portal user
02Customer-safe milestone
03Document request
04Approved file version
Current reviewVerify the customer and project relationship
Configured during assessment- 01Verify the customer and project relationshipCurrent decision
- 02Publish an approved milestone or requestNext controlled handoff
- 03Receive the customer action or documentNext controlled handoff
- 04Review and resolve the internal taskNext controlled handoff
Why this workflow breaks
Solar customers wait through design, review, permitting, installation, inspection, and activation while exchanging sensitive files. Internal project labels and shared email threads provide either too little clarity or too much operational detail.
Solar1 starts by documenting the decisions and failure paths. Configuration follows only after the operating boundary is understood.
Workflow sequence
Keep the handoff visible from first review to accepted outcome.
- 01Verify the customer and project relationship
- 02Publish an approved milestone or request
- 03Receive the customer action or document
- 04Review and resolve the internal task
- 05Expose the approved result to the customer
What to configure
Specific controls, qualified by implementation.
Configure document requests with type, due date, version, review, and access scope.
Define customer actions and route responses to an accountable internal owner.
Publish only approved files and statuses for the correct customer and project.
Assessment output
A shared definition of the records, owners, and acceptance checks.
Records in scope
- Portal user
- Customer-safe milestone
- Document request
- Approved file version
- Support ticket
Roles in the decision
- Customer success representative
- Project manager
- Customer
Checks before rollout
- Classify customer-visible statuses and files.
- Test project, file, and direct-link permissions.
- Define identity, access recovery, and support ownership.
Questions to settle
Questions to settle before configuring customer portal and documents.
What project status should a customer see?+
Use plain customer-safe milestones based on verified events, with approved context and any action the customer needs to take.
Can customers upload utility or permit documents?+
Document exchange can be mapped with required type, project, due date, review owner, version, and permission controls.
Can one customer access several projects?+
That access model can be configured after customer identity, organization, project relationships, and permission rules are validated.
Next step