App Auth Types

Dashworks allows users to connect apps at Org-wide and Individual levels, depending on the availability of APIs.

Individual connections can be established by any user in the workspace, connecting the app solely for their own use. Information within these Individual connections is not shared with anyone in the workspace who does not have access. On the other hand, Org connections can only be set up by Admins, and the app can be connected for everyone in the workspace at once. Dashworks uses "delegated access" for Org connections, ensuring that all individual-level permissions from the connected app are respected. As a result, individuals can only access content they have permission to view in the connected app. Under no circumstances can individuals who do not have access to a document, message, task, etc., see it in their Dashworks responses.

Are individual permissions respected for Org-wide connections?

Yes, Org-wide connections use user-level delegated access so that individual permissions are still respected based on the logged in user's email.

For instance, say you have setup an org-wide connection for Google Drive and a user with email [e-mail] signs up to Dashworks and asks a question. Dashworks will then check if the Google Drive has a seat assigned for [e-mail], and if it does, it will only return search results that the email has access to.

Is there ever a reason to have both an org-level and an individual level connector for the same source?

There are two cases when you may want to add an individual connection in addition to the org-wide one: 1) To search additional accounts: For instance, say you have a support inbox called [e-mail]. You would want to add it as an individual connection since the org-wide connection will only let you search the inbox for your primary email that you use to sign in to Dashworks. 2) To give the Bot Account access to a connection which has a different email: Say you have a bot account setup with the email [e-mail] but you want it to connect with the Zendesk seat for [e-mail]. In that case, you would add this Zendesk seat as an individual connection.