Client Portal Redesign — Layout & Hierarchy

Objective

  • Establish a foundational redesign of the client portal layout to improve usability, visual hierarchy, and brand clarity
  • Address recurring feedback that the current layout does not prioritize the right information for clients and agents
  • Create a parent issue to house related portal UX improvements as they are identified

Background

  • Initial feedback from Can surfaced two foundational concerns with the current portal layout:
  • The map takes up a disproportionate amount of space at the top of the portal and appears across multiple surfaces, pushing more relevant content down
  • The current layout does not clearly communicate company identity — agents opening the portal feel uncertain about which company it belongs to
  • Can suggested a stacked company info block positioned on the left side above "Progress" as a potential alternative to the current layout, similar in format to an email signature but more compact
  • Can explicitly noted inspector info should not be included in any persistent company block, as the assigned inspector may change between a client's initial portal access and when they later view their report
  • ATT-1953 addresses a near-term branding fix (full-width signature block on portal and quote screen) and should be treated as an interim solution ahead of this broader redesign effort

Product Decisions

Locked

  1. Inspector info exclusion — Inspector details should not appear in any persistent company identity block due to potential inspector changes across the lifecycle of an inspection

Open

  1. Map placement — Should the map be moved, reduced, or hidden by default? What is the intended role of the map in the portal experience?
  2. Company info placement — Is the left column above "Progress" the right position, or should this be revisited as part of a broader layout exploration?
  3. Scope of surfaces — Which portal views are in scope for this redesign effort?
  4. Relationship to ATT-1953 — Once this redesign progresses, does the interim signature block solution need to be revisited?

Scope

  • Frontend — Portal layout and component hierarchy across relevant views. Specific component files to be referenced once codebase access is available.

References

  • ATT-1953 — Add Company Signature Block to Client Portal and Quote Screen (interim branding fix)

Please authenticate to join the conversation.

Upvoters
Status

Planned

Board
🏠

Main App

Date

About 4 hours ago

Author

Linear

Subscribe to post

Get notified by email when there are changes.