Pipedrive Smart Docs: Your Documents Live in Your Drive, and That Decides Everything

Smart Docs will not create a single document until you connect a cloud storage account, and that requirement is the architecture of the whole feature rather than a step in its setup. Pipedrive's own knowledge base states that new documents automatically save to your selected drive, which means your quotes, proposals and signed contracts live in your Google Drive, OneDrive or SharePoint, and Pipedrive holds the link to them.

Almost everything teams find surprising about the feature follows from that one design decision, including who can open a template, why a shared document suddenly cannot be edited, and why the documents are missing from a Pipedrive export.

Pipedrive documents are managed from the Documents tab on a deal or contact, and Smart Docs is the feature behind that tab: templates, field population, trackable links, versions and eSignatures all sit there rather than in a separate documents area.

What it costs to have at all

Pipedrive's Smart Docs article, last updated 13 April 2026, opens with the plan boundary. Smart Docs is available on the Premium and Ultimate plans. Users on Lite and Growth can purchase the Smart Docs add-on, only users with account settings access can buy it, and the add-on includes a 14-day free trial with five signature requests, with billing details required to start the trial.

That matches Pipedrive's published plan feature table, which lists Smart Docs as a paid add-on on Lite and Growth and included on Premium and Ultimate. The same table shows Projects and LeadBooster following exactly the same pattern, which is the structural point worth carrying into a plan comparison: three of Pipedrive's add-ons stop being separate purchases at the same rung, so pricing a lower plan against a higher one on the seat rate alone will reliably get the answer wrong when you need two of the three.

The eSignature half carries its own note, and it is stricter than the feature note above it. Pipedrive states that eSignatures are available on the Premium and Ultimate plans, and only for users trialing those plans with valid billing details entered, while Lite and Growth users reach eSignatures through the Smart Docs add-on. A trial without billing details on file is a trial without signatures, which is worth knowing before somebody schedules an evaluation around getting a contract signed.

The storage connection is a permissions decision

Smart Docs supports Google Drive, Microsoft OneDrive and SharePoint. You connect from a deal or contact by opening the Documents tab and clicking Connect cloud storage, or from Tools and apps, then Documents, where you can add another provider or disconnect one. Pipedrive notes that connecting your Google account for Smart Docs is a different thing from setting it up for the Google Drive sync feature, which is the kind of distinction that produces a support ticket roughly once per rollout.

On Google Drive, Pipedrive automatically assigns a default shared drive folder for your company, and you can select a different one or create a new one from Google Drive's Shared drives tab and then point Smart Docs at it. Whether you take that default seriously is the decision that matters, because of what happens to templates.

Template sharing has two permission levels in Pipedrive: can use this template, which lets a user view and use it to create documents but not edit or delete it, and can edit this template, which allows all four. Then comes the sentence that catches teams out. Pipedrive states that users must also have access to the original template file in the connected storage provider, and recommends for that reason that all templates and documents be stored in a shared drive.

So access is a conjunction of two systems. A rep with the Pipedrive permission and no access to the file in Drive gets a template they cannot open, and nothing in the Pipedrive interface explains why. Creating templates has its own gate on top: the required Pipedrive permission is named as "Add and import Smart Docs templates", and only users holding it can create templates at all.

Before rolling Smart Docs out to a team

• ✓Yes: Your plan is Premium or Ultimate, or the Smart Docs add-on has been purchased on Lite or Growth
• ✓Yes: Billing details are on file, since the eSignature trial requires them
• ✓Yes: A shared drive is the storage location, not an individual's personal drive
• ✓Yes: Every user who needs a template has access to that template file in the storage provider itself
• ✓Yes: Whoever builds templates holds the add and import Smart Docs templates permission
• ~Depends: OneDrive users have pop-ups enabled, since the editor and file picker open in pop-up windows
• ✕No: Assuming a Pipedrive template permission is sufficient on its own

The two providers are not the same product

Pipedrive's documentation describes several behaviours that differ by storage provider, and the differences are large enough to affect which one you connect.

Creating templates and documents as a spreadsheet or presentation is only available for Google Drive users. OneDrive gets documents. If your quoting process depends on a spreadsheet with working arithmetic, that is a provider requirement rather than a preference.

Sharing works differently too. On Google Drive, the Share button inside the document editor offers three actions in one place: share as a link to a read-only PDF, request signatures, or download the PDF. On OneDrive and SharePoint you close the editor first, then use the three-dot menu on the document in the detail page to create a shareable link.

And OneDrive opens the file picker, template editor and document editor in new pop-up windows, which Pipedrive flags directly with instructions to enable pop-ups for Pipedrive in the browser. A first-run failure that looks like a broken integration is often a browser setting.

How fields populate, and why the first document is a data audit

Templates carry Pipedrive fields, and the mechanism is deliberately plain. You copy a field from the right-hand panel and paste it into the template body, where it appears in brackets in the form [Deal title (deal title)]. When a document is generated from that template, Smart Docs replaces the brackets with real data. Deal, contact, product, project and time-based fields are all available.

That is a more demanding use of CRM data than any report, because a report averages errors and a document displays them to a customer. A person stored with a full name in the first-name field, an organisation held under a trading name rather than the legal entity, a product priced indicatively for internal reporting: none of those are visible in a pipeline view and all of them appear in a proposal.

The cheap version of the audit is to generate documents from three real deals of different shapes before anybody sends one, and read every populated field rather than skimming the layout. Whatever is wrong in three is wrong across the pipeline. The structural fix, once you find the errors, is to decide which fields are allowed to feed a customer-facing document at all and keep the rest out of templates, because a document that pulls four verified fields and states the rest in prose is more robust than one that pulls twenty and is wrong about three. The identity question underneath the bad records is record matching, and it is worth settling in the CRM before it reaches a customer's inbox.

Versions are created by sharing, and they are immutable

This is the behaviour most likely to be read as a bug, so it is worth stating exactly as Pipedrive documents it.

Each time you generate a shareable link, Smart Docs creates a new version of the original document, including the number of views and the creation time. Once a version is shared, that version becomes read-only and cannot be edited. To update a document you open the original, make the change, and generate a new link, which appears as Version 2, Version 3 and so on beneath the original. Pipedrive recommends disabling older links where several versions exist, by opening the three-dot menu on the old version, choosing Share as link, and toggling off Enable link.

The model is a good one and it has a sharp operational consequence: a superseded quote stays reachable at its old link until somebody switches it off. Whoever sends a corrected price is responsible for disabling the version carrying the old one, and that step lives in a menu rather than in the send flow.

Tracking sits on the same mechanism. When generating a link you can enable view tracking and choose to be notified the first time the document is opened, every time it is opened, or never. Pipedrive states its document tracking feature is GDPR compliant and points to a separate article for the detail. Where your recipients are in the EU or UK, the wider question of what you may collect and on what basis is covered in GDPR for B2B outbound.

1. Step 1Create from a template

   Fields in square brackets are replaced with deal, contact, product and project data at generation time.

2. Step 2Generate a link

   This creates a version, records its creation time, and starts counting views if tracking is enabled.

3. Step 3The version freezes

   A shared version is read-only. Corrections go into the original document, not into the thing the customer is holding.

4. Step 4Re-share and retire

   A new link becomes Version 2. Disable the previous link, or the superseded document stays reachable.

What Smart Docs does not do

It does not put your documents inside Pipedrive. They are in the drive you connected, which has a consequence people meet at the worst moment: Pipedrive's export documentation states that files stored in Google Drive are not exported during global export. If your contracts are Smart Docs on Drive, backing up Pipedrive does not back them up, and that job belongs to whoever administers the storage provider.

It does not shorten the part of the sales cycle before a document exists. A quoting tool compresses the time between agreement and signature, which is real and narrow. Deals that stall in evaluation were never held up by the paperwork, and the stall usually starts earlier, in what was and was not established on the first call, which is the subject of running a discovery call.

And it does not fix a stage model that counts seller actions. A document sent is something you did, not something a buyer did, and a pipeline treating it as progress will report movement nobody caused. The distinction, and why every stage exit should be verifiable from the record by a third party, is worked through in defining SaaS funnel stages.

Smart Docs suitsNative, and inside the deal

• Quotes and proposals built from CRM fields you already maintain
• Teams already on Premium or Ultimate, where it is included
• Storage you already administer, in Drive, OneDrive or SharePoint
• Straightforward eSignature needs on documents generated from deals

Look further whenThe gates start binding

• You need spreadsheets or presentations and your provider is OneDrive
• Template access has to be managed in one system rather than two
• Documents must be retained inside the CRM's own backup scope
• Approval routing and redlining matter more than field population

Where we sit

RevenueFlow does not sell Pipedrive, resell it, or earn anything from a signup. We run cold email and LinkedIn outbound on Email Bison and HeyReach, and the account above is a documentation-grounded read of a feature we do not operate for ourselves.

It is worth writing anyway because quoting tools get bought to fix a symptom that starts further upstream. If deals close slowly because there are too few of them, the document layer is not where the time is going. Our campaigns send one message per prospect with nothing scheduled behind it, priced per qualified meeting against criteria agreed in writing before launch, and you can see what that looks like on your own market with a free campaign.

If the platform decision is still open, the Pipedrive alternatives roundup covers the field and Pipedrive against Salesforce is the head-to-head buyers run most, while Pipedrive integrations covers the ownership question every connected system raises.

Plan availability, the add-on trial terms, storage provider support, template permissions, field population, the version and tracking model, eSignature availability and the Google Drive export exclusion are per Pipedrive's own knowledge base, fetched 16 August 2026. Verify current terms with the vendor before relying on them.