If you need to restrict sensitive or confidential information to authorized users, then this template may be right for you. Right now, adding a user to a Coda doc means giving them the keys to the castle. This solution offers an alternative. It’s quick to setup, easy to manage, and doesn’t compromise on security.
Quick Start Guide
Cool, how does it work?
Fancy a look under the hood? Here’s a high-level introduction to this template’s features and a basic run-through of how the solution works.
table stores confidential information using encryption. What this means is that sensitive text is transformed into a gibberish string of characters that cannot be decrypted without knowing the password originally used to encrypt it.
When creating a new item, the user enters a password which is used to generate an encryption key. An encryption key is a long string of characters used by the encryption algorithm to transform the original text into an encoded state. Sensitive information is only ever stored encrypted within the Doc. At no time are the password or the unencrypted text ever saved to a table, synced to Coda’s servers, or made visible to other users within the doc.
To access the encrypted information, the same password must be provided. The encryption algorithm is effectively reversed, and the unencrypted content is made visible to the authorized user. Importantly, this all happens within a secure sandbox.
While the item is visible to the authorized user, it’s not decrypted in the table, not synced to Coda’s servers, and not visible to other users.
For a walkthrough detailing each step of the solution and all the security features in place to keep your information safe, head to