Lovable: Per-User GitHub Connections for Published Apps
LovableLovable extended its GitHub API connector to support per-user access through app user connectors, letting each person who uses a published app connect their own GitHub account instead of sharing one workspace-wide connection. Actions then run under that individual's own GitHub permissions rather than the builder's, making the feature well suited to issue dashboards, PR trackers, and other GitHub-backed tools shared across a team. Builders set it up once, from Connectors → GitHub API → Add connection → App user connector.
Key Takeaways
- Per-user GitHub access replaces the old one-account-for-everyone model for published apps that need to call the GitHub API.
- Each app user now authenticates with their own GitHub account, and the app can only read or write what that person is already permitted to touch.
- The feature is distinct from Lovable's existing GitHub Git sync, which only syncs a project's source code and has nothing to do with runtime API calls.
- Builders need to create one GitHub OAuth app per workspace and add it as an "App user connector" before end users can connect individually.
- The update is best suited to team-facing tools like issue dashboards and PR trackers, where GitHub's own permission boundaries need to carry through to the app.
- It's part of Lovable's broader app user connectors framework, which already supports per-user access for services like Amazon Redshift.
A New Way to Connect GitHub
Lovable extended its GitHub API connector to support per-user access through app user connectors. Previously, a published app's GitHub integration worked through a single shared connection: one account, configured once, that every visitor to the app used. Now, each person who uses a published Lovable app can connect their own GitHub account instead, and the app reads and writes only the repositories, issues, and pull requests that person is actually permitted to access.
How It Differs From Existing GitHub Integrations
This is distinct from two other GitHub-related features already in Lovable. It is not the same as a standard GitHub API connection, where the builder connects one account and every visitor to the app shares it. And it is not the same as GitHub Git sync, which syncs a Lovable project's own source code to a repository rather than letting the app call the GitHub API on a user's behalf.
Setup for Builders
To use the new mode, a builder creates one GitHub OAuth app for their workspace, then adds it from Connectors → GitHub API → Add connection → App user connector. From that point on, each person using the published app signs in with their own GitHub account the first time they touch a GitHub-connected feature, and every subsequent action they take runs under their own permissions rather than the builder's.
Why It Matters
The change matters most for apps built to sit on top of GitHub as a workflow tool — things like issue dashboards, PR trackers, and internal tools shared across a team. Without per-user access, every action taken through the app effectively ran as the builder, which meant permission boundaries between team members were invisible to GitHub itself. With per-user connectors, an app can now respect the same repository- and issue-level permissions GitHub already enforces, without any extra code from the builder.