Manage Page Visibility

This guide shows you how to manage page visibility in QuoteCloud documents, allowing you to control which pages are displayed under specific conditions or to certain users.

Manage page visibility

1. Hide pages from document recipients when needed.

2. Restore hidden pages to make them visible again.

FAQs

What is Page Visibility in QuoteCloud and why should I use it?

Page Visibility is a feature in QuoteCloud’s document editor that lets you control which pages are displayed in a generated document based on conditions like user role, customer data, product selections, or quote value. Use it to create dynamic, tailored documents that present only relevant information to each audience—reducing clutter and improving the buyer experience.

This capability is especially useful for sales quoting software and sales proposal software workflows where different stakeholders (e.g., internal reviewers, clients, finance) need different content in the same template.

How do I create and edit visibility rules for a page?

Open your document in the QuoteCloud editor, select the page you want to control, then open the Page Visibility or Conditions panel. Choose the condition type (role, field value, product selection, quote total, custom variable) and define the rule. Save the rule and publish or preview the document to verify behavior.

Common steps: 1) Select page → 2) Click Visibility/Conditions → 3) Pick condition(s) and logical operators → 4) Save and test. These rules work across templates so you can reuse them in your proposal software templates.

Can I show different pages to internal users versus external customers?

Yes. QuoteCloud supports role- and permission-based visibility so you can hide internal-only content (cost breakdowns, internal notes, negotiation guidance) from external recipients while keeping client-facing pages visible. Set the rule to show a page only when the viewer role is 'internal' or when the document is viewed in internal preview mode.

This makes it easy to use one document template for both internal review and final client delivery when using quote software or proposal software.

Do visibility rules work with templates and branding?

Visibility rules are applied at the page level and are preserved when you save or clone templates. That means you can build a single branded template (with your colors, logo and style) and use visibility rules to create multiple tailored versions for different industries, customer segments, or products.

Using visibility with templates reduces duplication and ensures consistent branding across all sales proposals and quotes generated from the same template.

Can I use Page Visibility with interactive pricing or sales quote tables?

Yes. Page Visibility can respond to selections made in interactive pricing tables or other fields. For example, selecting an optional service in a pricing table can reveal a detailed scope page, or removing a line item can hide warranty pages. This enables highly personalized quotes and proposals and shortens sales cycles by surfacing only relevant options.

It’s a powerful combination for sales quoting software and sales proposal software workflows that include configurable products or tiered pricing.

How does Page Visibility affect integrations like QuickBooks Online and e-signatures?

Visibility controls what appears in the delivered document and PDF exports. Transactional data used by integrations (e.g., items, totals, customer records synced to QuickBooks Online) are driven by the underlying document data, not the visual page visibility. That means hidden pages won’t show in the PDF or client view, but line items and amounts can still sync to accounting software if they exist in the document data model.

For e-signatures, ensure pages that require signer interaction are visible for the recipient. If a signature block is hidden by visibility rules, the recipient won’t be prompted to sign it.

How can I preview and test page visibility before sending a document to a client?

Use the editor’s preview mode and its role/viewer simulator to test different visibility conditions (client view, internal view, specific customer data). You can also create sample records or use test data to simulate field-based conditions and product selections. Share internal review links to confirm how the document renders for colleagues before sending.

Testing prevents errors like accidentally hiding required signature pages or exposing internal notes in outgoing proposals.

Best practices for using Page Visibility at scale in high-volume document production?

Keep rules simple and well-named, reuse visibility conditions via templates, and document the logic so team members understand which pages appear under which conditions. Use consistent variable names, group related conditions, and maintain an audit log or version history for templates that control critical quote or contract content.

These practices improve reliability when producing many documents—particularly for teams using QuoteCloud as quote software or proposal software for high-volume workflows.