When you install a Pack, there will be a step where you give Coda access to work with the other app. We get it - sometimes these permissions can sound a bit intimidating. But, not to worry. You can decide exactly how much access to give based on your needs.

If you are only using a Pack to push Coda data out to places like email and Slack, your Coda app will not have read access.

If you are using a Pack to pull in information to connect the apps you use everyday via your Coda docs, then the read access is there for you to control. Remember, that you also have full control over who can work with the data inside your Coda doc through your sharing settings.

Here's an overview of how Packs work behind the scenes (in this example, we'll use Gmail, but the same principle holds true for other apps):

  1. You open up Packs and click Sign in to Install
  2. You sign in to Gmail using your app credentials. 
  3. Gmail sends an Authorization Token back to Coda which gives Coda access to do things to and from Gmail on your behalf
  4. In Coda, you add a Gmail Button to send emails out from the Coda doc
  5. You (or an automation you made) click the Gmail Button, Coda makes a call to Gmail using the Authorization Token to ensure that it's still active. If it is, Coda makes a call to the Gmail servers and sends an email through Gmail, passing in Coda data into the message container. 

In the example above, Coda does not access your Gmail in anyway.

If you have further security questions, feel free to reach out to us at support@coda.io.

Did this answer your question?