OAuth Apps
Most connectors authenticate with OAuth. By default, connections use Flobyte's shared OAuth application — but you can bring your own OAuth app so every connection is branded and controlled by you, not us.
This is managed by the platform (your admins) or, when Flobyte is embedded in your product, by your developers through the SDK.
Why bring your own OAuth app
- Your branding — users see your app name and logo on the consent screen, not Flobyte's.
- Your scopes — request exactly the permissions you need, and nothing more.
- Your control — rotate secrets, revoke access, and manage rate limits in your own developer console.
- No shared limits — you're not sharing OAuth quotas with other Flobyte customers.
Configure a custom OAuth app
For each connector you want to control:
- Create an OAuth application in that provider's developer console (e.g. Google Cloud, the Microsoft portal, the Slack API dashboard).
- Set the redirect URL to the one Flobyte shows for that connector.
- In Flobyte, open Platform Settings → OAuth Apps, pick the connector, and paste in your Client ID and Client Secret.
From then on, any new connection for that connector uses your OAuth app.
Existing connections keep working on whatever app they were created with. Re-create a connection to move it onto your custom OAuth app.
Managed by the platform or by developers
| Who | How they manage OAuth apps |
|---|---|
| Platform admins | In the UI under Platform Settings → OAuth Apps |
| Developers (embedding) | Programmatically via the SDK when provisioning a platform |
Governance
Custom OAuth apps work hand-in-hand with governance: credentials are stored in the encrypted vault, connections are scoped per project, and every use is captured in the audit log.