The Proposals page

Updated August 14, 2026

Click Proposals in the sidebar to see every proposal that has been built or saved in your workspace. It is the default landing page when you sign in.

#What the page shows

The heading reads Proposals. The subhead changes by role: the agency owner sees Every proposal in the workspace. Producers only see their own., while a producer sees Your proposals. The owner sees the whole book.

Below the header is a table of rows, one per proposal. Each row shows the client name, the owner (the producer who built or saved it), the type (New business or Renewal, depending on whether the proposal has a comparison slide), a status pill, and when it was last touched. See Save a draft and the pipeline stages for exactly what each status pill means and how it gets set.

Click New proposal from the page header at any time to start a new one, which takes you to the New proposal page.

#Reopening a proposal

Click anywhere on a row to reopen that proposal. It opens straight into the presenter view, exactly as it was when it was built or last saved, ready to review, edit, or present again.

#Who sees what by role

  • The agency owner sees every proposal in the workspace, every producer's work, all in one list.
  • A producer sees only the proposals where they are the listed owner.

This mirrors the same owner-versus-producer split used across the rest of the app. See Signing in and user roles for the full breakdown of what each role can see and do.

#Saving a proposal to this list

Building a deck does not automatically put it on this page. From the presenter view, click Save to add it here. You will see a confirmation: Saved to ProClose. "\<client\>" is in your Proposals list as a draft.

Saving is real, durable storage, not a session trick. Clicking Save posts the proposal to your workspace's own server, which writes it to a database row scoped to your tenant and to you as the owner. Reopen it tomorrow, from a different machine, after signing out and back in, it is exactly as you left it, because it never depended on the browser tab staying open. If the save call cannot reach the server (you are offline, for instance), ProClose still adds the proposal to the list you see so the click never looks like it silently failed, but it says so plainly: Saved locally. The proposal only lives in this browser until you save it again once you are back online. See Where your data lives for the full picture of what is stored where.