6 days ago
I added someone who is also a admin on github for a project so i added them to the railway space with that same email so that we could avoid the manual deployment approval, but its still making me approve and says insufficient permissions for them.
2 Replies
6 days ago
This is a question about using Railway itself, and the quickest answer usually comes from people who have set up the same thing and can tell you how they got it working.
So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public and the thread closes.
Status changed to Awaiting User Response Railway • 6 days ago
6 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 6 days ago
6 days ago
Have the other person (the GitHub admin) do the following:Accept the invite
Check the email you used when inviting them and make sure they clicked the invite and joined the workspace/project.
You can verify this in Railway → Workspace settings → People (or Project settings → Members).
Link GitHub to their Railway account Log into Railway with the account that has the invite.
Go to Account Settings → Integrations (or Connected Accounts).
Connect / authorize GitHub.
Make sure the correct GitHub user is linked (the one that has admin rights on the repo).
Confirm they appear as a member Workspace level: Admin / Member / Deployer — any of these works.
Or add them directly to the project (Project Settings → Members) with Editor (or even Viewer in some cases). Project-level is often the cleanest.
Re-trigger a deploy
Push a new commit (or re-run the latest one). It should now auto-deploy without approval.
Extra checks if it still failsThe Railway GitHub App must have access to the repository (GitHub → Settings → Applications → Installed GitHub Apps → Railway → Configure → repository access).
The person must have write/contributor access on the GitHub repo (they do, since they’re an admin).
Sometimes a disconnect + reconnect of the repo in the Railway service settings (or a refresh of the GitHub integration) is needed after adding the user.
If the commit was made via a merge from a fork or by a bot, it can still be treated as external.