Using published docs as client portal

Ask the Community
1

I am building a Quality Management System (QMS) in Coda.

I ran some tests and really liked the experience of a published doc: cleaner top navigation, more usable screen space, and a feel much more like a client-facing portal than a standard Coda document. This could make it easier for non-technical users to navigate through documents, risks, non-conformities, action plans, training modules, and other sections.

My question is: what are the practical advantages and disadvantages of using a published Coda doc as a client-facing portal, while restricting access to invited users only?

More specifically, I’d like to hear from anyone who currently uses or has used this approach.

2

This works pretty good.

You have to make an account for everyone who is going to get access, and you have to double-check all the settings.
You can prevent copying; you can prevent unauthorized access. Your users will have access to the regular SH doc and the published doc, make sure the settings for the accounts are view only.

You can also share without accounts by means of a private links (you can limit dicoverability), but once someone has the link, you can’t undo access to that person.