Q: What is the correct redirect URL for Caddi?
A: https://app.trycaddi.com/oauth-callback
Q: What Oauth scopes does Caddi recommend using?
A: Generally Caddi recommends using the maximum set of Oauth scopes that relate to end-user needs in a given platform, such that Caddi would be expected to be able to perform all functions that end users generally do. This would generally mean full read+write permissions (read or create files), but not admin permissions (create or delete users).
Admins must also ensure the addition of required Oauth and OIDC scopes such as refresh_token and profile (varies by integration) - without these, Caddi is not able to do necessary authorization actions.
All integrations Caddi supports have a default set of scopes, and custom integrations are encouraged to use those.
Q: What authorization flows does Caddi support?
A: Caddi prefers standard Oauth2 integrations as a default, and will always use Oauth2 flows unless the provider does not support them. Some situations require other auth approaches such as service principals, API keys, Oauth1, etc.
Q: Who can configure custom integrations?
A: Organization owners and admins can configure custom integrations. Organization members cannot modify integrations.
Q: If my organization has a custom integration, can users still use the standard Caddi-provided integration?
A: No, a custom integration replaces the standard integration for users in the organization. Once configured by an admin, members of an organization would be disconnected (tokens revoked) from the standard connection and only see the ability to connect to the custom integration.
Similarly, for multi-integration situations such as Microsoft (Teams, Outlook, etc) or Google (Gmail, Docs, etc) - when the high-level integration is configured by an admin all individual integrations are "collapsed" and hidden from users. That is, if a custom Microsoft integration is configured, users will no longer see the option for Outlook, Teams, Sharepoint, etc.