How-to · Lesson 6 of 19
OAuth Integrations: Tools That Act as the User
A shared service account can send an email, but not as you. OAuth lets a tool act on behalf of the person who signed in: register the OAuth app once for the organization, then each person connects their own account.
What You Will Learn
- The two halves of OAuth: the organization registers the app once, then each person signs in to connect
- The OAuth Integrations page, and what Configured, Using Global and Not Configured each mean
- Entering your organization's own client ID and secret instead of relying on the global credentials
- The user flow: Connect, sign in with the provider, approve the consent screen, and land back on a connected tool
- Where the tokens go: into the vault, tied to the connection, never into the workflow
- Scope and identity: a personal connection acts as you, a project connection is one account shared with the team
- What happens when an organization's credentials are deleted: the integration falls back to the global ones