Settings and activity

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Lachy Wharton supported this idea  · 
    An error occurred while saving the comment
    Lachy Wharton commented  · 

    +1 on this. This is actually really, really important to our business.

    PandaDoc currently publishes your template changes as you make them. While this is undoubtedly a handy feature for some, it's actually a real drawback/problem for us.

    The vast majority of our PandaDoc usage is via the API and, using the API, we are generating dozens of documents from templates every hour. This means that there is a high chance that a document would be created from a template while that template is being edited. That means the document could have the change only partially implemented, or it could have errors if the change hasn't been reviewed and approved for release yet.

    As a high-volume API user, we really need control over when our changes are published. This is critical.

    The workaround we have for now is that we will only edit templates outside business hours when we are confident documents are not being generated. That's a really bad situation for us to be in.

    Would love to have the ability to turn off auto-publishing of changes and instead have an option to only publish changes on demand (i.e. push a button to publish changes to template).

  2. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Lachy Wharton commented  · 

    Big +1 on this request.

    We have a use case in our business as follows:

    Within bundle:
    * Doc 1 - must be signed by A and B
    * Doc 2 - must be signed by A and C

    For privacy reasons (read: legal requirement), C should not be sent and should never see Doc 1.

    So ideally:
    * Doc 1 is sent to A and B only (even better if we can optionally add C as a "cc"/viewer)
    * Doc 2 is sent to A and C only (even better if we can optionally add B as a "cc"/viewer)

    As normal, the bundle is complete once (1) A and B sign Doc 1; and (2) A and C sign Doc 2.

    Lachy Wharton supported this idea  · 
  3. 359 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Lachy Wharton supported this idea  · 
  4. 133 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Lachy Wharton commented  · 

    Very keen to see this implemented. This would be very beneficial. Think about monstrous terms and conditions that are used in several templates, I want to be able to updated these once in the content library item and have those changes propagate out to all templates that use them.

    To do this safely, you could consider that templates using the content library item do not automatically update. Rather you can go into those templates and "pull" in the latest changes.

    Please implement this!

    Lachy Wharton supported this idea  ·