Publishing to your Team

How to publish a doc internally

Updated over a week ago

Inside this Article

After launching publishing, we heard that our newer features would be helpful for teams using Coda to collaborate within their domain, and not just for docs to be shared with the world wide web.

As a result, we added some more options to your sharing settings so that you can use features like interactivity modes and top navigation for the docs intended just for your team! To access these new options click "Share" and then select "Publish" at the top of the sharing menu.

More Details

🌟 Please note, only the Doc Maker may publish Docs or Forms. 🌟

  • By default, your discoverability settings will be toggled On. This means if you are part of a team's managed domain, upon completing the steps to publish your doc, it will not appear listed on your maker profile (here's an example); note that if you want a maker profile, you will need to publish a doc to the world wide web with Discoverability switched to on

  • Anyone in your domain will be able to access your published doc at the link you specify; anyone from outside your team who tries to access the doc will see a message that they don't have access to the doc

  • All other publishing features can be used as expected within your team:

  • Doc Interactivity: Can people just read the doc? Play with various calculators in the doc? Make contributions to the doc, like adding rows to a table or voting on topics? You choose!

  • Copy: You can add a copy button to your doc to make it easier to replicate for things like internal templates, etc.

  • Show sections in top nav: You can give your doc a more website-like feel with the top nav 

  • Visual Options: Published and unpublished docs have access to a variety of visual options, including cover images, subtitles, author bylines, font styles and sizes, section outlines, and more.

❗️IMPORTANT: If you do not have a domain (ie. set up as your login with Coda, the above does not apply; even with discoverability settings toggled off, publishing a doc will still share to the world. ❗

We hope this new option helps you use Coda to make and share polished executive dashboards, team wikis (with a controlled group of editors), or internal modeling tools that feel less "breakable" to your teammates.

But what if you do want to publish a doc to the web on behalf of your team, or have it listed on your public maker profile? Simply toggle the "Discoverable to anyone" switch to "On" and it will be available to anyone with the published linkーwhether they are shared the link directly, find it via search engines, or click it from social media sites where it has been shared.

And don't worryーnot everything about sharing docs is changing. When you make a new doc, it is still only accessible to you by default. When you click the "Share" button in the upper right-hand corner of a Coda doc and make selections in the "Share" menu that pops up, your options for inviting teammates in the same Coda workspace as Editors, Viewers, etc. also remain unchanged. 


Can I publish to just my team?

Yes! You can read more about that here: It works on the same system (i.e, you publish from your username) but allows you to set it so that only folks in your company can see it.

Team publishing requires that everyone is on the same approved email domain!

If I publish my doc and it contains packs that connect to my personal accounts (Gmail, JIRA, drive, etc.), will my personal accounts be kept private and protected?

Yes - you can make sure that your personal accounts are protected by publishing your doc in View mode. This will prevent viewers from taking any action with those packs. When they copy your doc, any pack connections to the publishers’ accounts will be removed, and the new user will be prompted to connect to their own accounts.

You need to be more careful if publishing in Play or Edit mode. These modes allow viewers to push buttons and take actions in your doc. If you need to publish in one of these modes, make sure any packs are relying on Private Connections (rather than Shared Connections) for button actions. This will make buttons act as the current user.

My published doc is in edit mode but my form (in-doc form view of a table) is shown as play mode. What’s going on?

Make sure the user is signed in. If the user is signed out and looking at a published doc (edit mode), the doc goes into play mode. They’ll need to log in.

Did this answer your question?