Evaluating client-facing access and tracking

What client-facing access and tracking covers

Client-facing access and tracking covers two linked questions. Who can open, collaborate on or edit a page or document? What activity can you observe once it is shared?

Evaluate the questions together: the access route determines what the tracking data actually represents. A public link, a verified viewer and an internal colleague all reach the same page by different doors.

Some settings do both jobs at once. In Qwilr, identity verification restricts who can open a page; once someone verifies and views it, their details appear in page analytics. The gate and the report are the same feature.

This matters when reading engagement numbers. A high view count on a public link is not the same evidence as a named verified viewer.

Access levels and sharing routes

Qwilr offers three internal sharing routes, depending on how much access a colleague needs. Team members in your Qwilr account can receive View-Only or Edit Access. Team members outside your account can receive a Collaborate link, which lets them view the page but not make changes.

Edit access requires a Qwilr account. While editing a page, click Collaborate in the top right, open the account's current users and select the person. The default is Can Edit; a dropdown switches it to Can View.

Inviting someone who is not already in your Qwilr account invites them to join the team, adding a licensed seat and its billing. Check who is already licensed before granting edit access.

Externally, every new Qwilr page starts in Draft with its public link deactivated. To publish, click Share from the Dashboard or inside the page and use the dropdown to set the page Live; this automatically copies the public page link to your clipboard.

The Copy Shareable Link button sits at the bottom of the same pop-up, which also holds optional security settings such as password protection and view limits.

Client Access Routes in Qwilr: Internal vs External Sharing

Identity verification and domain gating

Qwilr identity verification is available on Growth and Scale plans and the legacy Enterprise plan. Add a verification step to any page so clients must enter their email before viewing it. The setting can also apply to a template, so verification applies automatically to every page your team creates from it.

To set it up, click Share from the dashboard or page editor, open Access settings and tick Email Verification. Ticking it also lets you select Domain Security, limiting access to viewers whose email comes from an approved domain or set of domains. Enter domains separated by commas, without the @ symbol.

If you only want names or email addresses for tracking and analytics rather than a login step, tick either or both of the Identification options, Name and Email.

Buyers see a form. With email authentication, they enter their name and email address, then receive an email with a link to verify that address; once verified, they can view the page. Buyers with a Qwilr Springboard account can log in with it to populate their name and email.

Verified details feed the reporting. Once someone verifies their identity and views the page, that information appears in your page analytics. On Scale plans with identity verification, if the viewer provided a name or email, you can open their LinkedIn page from the session view.

Publishing a Qwilr Page with Identity Verification

Pros and Cons of Identity Verification in Qwilr

Version control and sent document integrity

Version history and the consequences of editing a sent document: see Testing proposal version history.

Approval workflows before a client sees anything

Approval routing for a sales proposal, including approver groups and role permissions, is covered in Checking approval workflows for a sales proposal.

Engagement analytics at page and block level

Once a Qwilr page's public link receives its first view, an ongoing view count appears on the Dashboard and updates automatically each time a buyer views the page. Views by your logged-in users and admins are not counted, so the count reflects external audience activity.

Automated traffic can still register. Notifications can appear to come from real viewers but be triggered by bots or automated systems, such as preview services used by Microsoft, Outlook or antivirus scanners.

Qwilr does not currently support IP address blocklisting, so these cannot always be suppressed. A workaround is to link the page URL behind a button or phrase such as View Proposal rather than pasting the raw URL.

Page analytics show each viewer's location, the date and time they viewed the page, how long they stayed, and which sections they spent the most time on. The Viewers tab can be filtered by country; the individual Viewers card adds Session View, Timeline, Time spent and Interactions.

Session view holds the detail: viewer details, the time of the visit, its duration, the visitor's location, and the device and browser used.

Embedded pages are a known gap. Qwilr pages embedded in other websites do not track analytics or page views consistently; the recommended approach is to set them up as external hyperlinks that open in new tabs, or send them directly.

Structural changes blur block-level data. If you replace or remove blocks from an ongoing page, the block name is listed as Deleted Blocks and aggregated as a group, in both group averages and calculations and the individual statistics for each view.

Qwilr Engagement Analytics: Key Metrics

Document and recipient tracking

PandaDoc Document details, available on Starter, Business and Enterprise plans, previews a document's information without opening it, covering recipient analytics, general details and an audit trail. Open it from the three vertical ellipses on the right of a document and choose Document details.

Under Analytics, check who has not yet signed and send them a reminder, and review how much time each participant spent on each page. Under Details, check when a document was created and sent, when it will expire, and when it is set up for renewal.

Recipient analytics opens from the three-dots button to the right of a recipient's name. It shows how much time that recipient spent on each page and in total, when they last viewed the document, whether they downloaded it, and more.

The audit trail gives a step-by-step history of all the document's status changes and is available only on sent documents. Latest activity, on the same Document details tab, is a record of every action taken on the document.

Expiration dates are checked or edited under File then Document then Expiration, and reminder settings under File then Recipients then Reminders. On Enterprise, the Company field auto-populates from values recognised in the document contents for uploaded PDFs and PandaDoc documents, letting you filter documents by company name; it can also be filled in manually.

Status lifecycle and follow-up

Every Qwilr page shows a current status. Draft means the page is in progress and not yet shared; Live means it is active and shareable; Pending means it is awaiting client acceptance; Accepted means the client has accepted the page.

Declined applies only to pages with an expiry set that have not been accepted, or that a Qwilr user has manually declined. A proposal cannot be declined by the end customer receiving it.

The dashboard status is the fastest follow-up signal, showing at a glance which pages a client has accepted so you need not open each one. Sorting the page list by Last viewed or Page views brings the pages drawing the most attention to the top.

On the PandaDoc side, expiry and renewal information in Document details marks when a document lapses or is due to renew. Reminder settings control which follow-up emails go out, and recipient analytics identifies who has not signed so reminders reach the right people.

Document Status Lifecycle in Qwilr

Organising pages and shared content

Qwilr organises pages with tags, folders and sorting. Dashboard sorting options are Last edited, Date created, Alphabetical, Last viewed and Page views, in either direction; tags help a team filter the dashboard to find specific pages.

Reusable content libraries and cross-workspace content sharing are compared in Comparing reusable content libraries.

Limitations and caveats

Weigh the limitations described alongside each feature when evaluating client-facing access and tracking.

Pre-Publish Checklist for Client-Facing Qwilr Pages