Included in this article:

How do I copy a published doc?

There are two possible ways to copy a published doc. Many docs created with the intent to be copied will have a “copy” button on it.

If there is no “copy” button on the published doc, you can copy the doc by using the menu next to the title of the doc. Once you copy the doc, you will have your own version in your own workspace.

Key Points:

  • A copy of this doc will live entirely as its own, unconnected doc in the workspace of the user who copies it.

  • Edits will not impact the source doc.

  • There are no connections between tables of the source doc and the new, copied doc.

How do I copy a published a doc that is open only to my team?

You can copy a published doc with publishing features that is ONLY available to users in a specific workspace or organization in the same way that you copy any published doc.

The main difference here is the availability of the doc. As opposed to a general published doc, a doc that is available only to your team can only be copied by people on your team.

Key Points:

  • A copy of this doc will live entirely as its own, unconnected doc in the workspace of the user who copies it.

  • Edits will not impact the source doc.

  • Cross-doc connections may persist, meaning a user with appropriate permissions in their team could re-establish a cross-doc connection to receive data from the source table. However, they new, copied doc cannot write to the source table.

Learn more about publishing only to your team here.

How do I make a doc copyable?

You can put the “copy doc” action in a button so that anyone can click the button to make a copy of the doc, which will then live in their workspace. This is also possible by hovering over a doc title and selecting “copy.”

Key Points:

  • Any copy another user makes of your doc will live entirely as its own, unconnected doc in the workspace of the user who copies it.

  • Edits to any copied doc will not impact your original doc.

  • Cross-doc connections may persist, meaning a user with appropriate permissions in your team could re-establish a cross-doc connection to receive data from the source table. However, they new, copied doc cannot write to the source table.

How do I make a page copyable within a single doc?

You can put the “duplicate page” action in a button so that anyone can click the button to make a copy of the page, which will live in the same doc. This is also possible by hovering over a page title and selecting “Duplicate.”

Key Points:

  • A copy of this page will live in the same doc as the original page.

  • Edits to the page canvas will not impact the source page.

  • Edits to tables on the page may impact the source page, depending on (1.) whether the page was copied via duplicate page action or duplication from the page list*, and (2.) settings indicated by the maker who added the cross doc action

*For #1 above, if the page is copied via duplication from the page list, tables will all be connected views unless the copier selects “Paste data instead” from the toast that appears after duplication. If the page is copied via duplicate page action, the settings indicated by the maker who built the action (button) will be honored.

Find out more about page duplication here.

How can I keep track of pages that are duplicated?

When you add a duplicate page button column to a table, you can optionally retrieve & store the URL for newly created pages in another column of your choosing. Here’s how:

  1. Add a new column, and select the “Button” type

  2. While configuring your button settings, select the “Duplicate page” button type

  3. After making your selections for which page to copy, how to handle data duplication, etc., you’ll see a drop-down menu for “Results Column (Optional)”

  4. Simply select the column that should populate with the results when a page is copied to start building your index of copied pages

Screen Recording 2021-03-25 at 11.29.45 AM.gif

How do I make a template for my team (beta)?

Rather than build a doc and have people copy it, you can intentionally make a template which can be discovered as a template in the doc list. From there, it can then copied and used as a new doc by your team members.

Key Points:

  • Any copy another user makes of your template will live entirely as its own, unconnected doc in the workspace of the user who copies it.

  • Edits to those copied templates will not impact the source template.

  • Cross-doc connections may persist, meaning a user with appropriate permissions in their team could re-establish a cross-doc connection to receive data from the source table. However, they new, copied doc cannot write to the source table.

This feature is currently in beta, and we are not accepting new testers at this time.

Did this answer your question?