11 days ago
Hi Railway team,
We're on the Pro plan and have reproduced what appears to be an authorization mismatch between the Railway dashboard and CLI/API.
A project member with the “Can View” role can open and read deployment/build logs in the dashboard. However, the same user's account token, used by the official Railway CLI through RAILWAY_API_TOKEN, receives:
Unauthorized
Command shape:
railway logs --project [project-id-here] --environment [env-here] --service [service-here] --build --lines 1
We controlled the test as follows:
- With the member set to “Can Edit,” the account token and command succeed.
- We changed only the member role to “Can View.”
- The dashboard still displays deployment logs for that user.
- The identical CLI command then returns Unauthorized.
- The token remains valid and can read project/deployment metadata.
Expected behavior:
A Viewer's CLI/API log permissions should match the dashboard's read-only log access, while deployments, variables, and configuration mutations remain denied.
Could you confirm whether this is expected, a known API authorization gap, or a bug? Is there a supported read-only token or OAuth scope for retrieving build and deployment logs?
1 Replies
11 days ago
Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.
This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves 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. The thread closes, since this isn't something Railway support can take further.
Status changed to Awaiting User Response Railway • 11 days ago
11 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 • 11 days ago