Railway authenticates through external providers, and we cannot change which GitHub account is linked to a Railway account, swap login identities, or otherwise modify account access on our side. This is a security boundary that protects the account, not a policy limitation.

If you can sign in with the GitHub account sahajpreetk381-collab that Railway recognizes, that sign-in reaches the Railway account and its projects. If your projects appear missing after signing in, you may be landing in a different workspace than expected - check the workspace switcher to confirm which workspace is selected. If you have another login method (Google or email) already linked to that account, signing in with it reaches the same account. Otherwise, recovering or managing access to the correct GitHub account through GitHub is the path forward.

The automated response does not resolve my issue. I can successfully authenticate with the GitHub account Railway identifies (sahajpreetk381-collab), but I still cannot reach the original Railway projects through the dashboard. I also have an active Railway CLI session that can access the original workspace/projects. Please have a Railway employee review why the dashboard account/session is not exposing the same workspace and projects.

The account you are currently signed into (linked to GitHub sahajpreetk381-collab) was created on 2026-08-01 and has no projects in it. Your original projects are not missing - they live on a separate Railway account that was created with a different sign-in method. Your CLI session is still authenticated to that original account, which is why it can see the projects. Signing in with the GitHub account sahajpreetk381-collab reaches this newer, empty account instead. If you originally signed up for Railway using a different GitHub account, Google, or email login, signing in with that same method will take you straight to your original account and its projects.

I originally accessed this Railway account using Sign in with Apple / Apple ID, and the account used Apple’s Private Relay email. I have not intentionally changed the original Railway login method.

The current GitHub login takes me to a newer empty Railway account, while my CLI is still authenticated to the original account and can access its projects.

Why is the original Apple ID / Sign in with Apple authentication no longer taking me to the original Railway account?

Could you please check whether the Apple/Private Relay identity associated with my original account is still correctly linked, and whether there is an authentication issue preventing Sign in with Apple from resolving to that account?

We cannot inspect or modify which sign-in identity (including Apple ID) is linked to any Railway account, so checking the Apple/Private Relay association on the original account is not something we can do on our side. This is a security boundary, not a limitation we can work around.

Since your CLI session is still authenticated to the original account, running railway whoami in that session will show the login email on it. That email tells you which sign-in method reaches it, and signing in on the web with that same method will take you to your original account and its projects.

Thanks. I understand the security boundary and I'm not asking Railway to reveal credentials or bypass authentication.

The issue is specifically that my original Railway account was accessed through Sign in with Apple / Apple ID using Apple's Private Relay, and my active CLI session is still authenticated to that original account.

railway whoami only confirms the Private Relay email attached to that session; it does not tell me why Sign in with Apple no longer resolves to that same Railway account.

Could you clarify one specific point: Is Sign in with Apple still supported for existing Railway accounts, and if so, why does my Apple ID now resolve differently from the original account that my CLI session still accesses?

I'm not asking you to disclose or change the login identity. I just need to understand why the authentication behavior changed for this existing Apple-linked account.

I understand. Since the CLI session is still authenticated to the original account and can access the original projects, I don't want to risk logging out or changing that session.

The remaining issue is that the original account was accessed using Sign in with Apple / Apple Private Relay, but the web authentication no longer reaches that account.

If Railway cannot inspect or modify the Apple identity linkage, is there any supported way for me to restore web access to the existing account without logging out of or invalidating my current CLI session?

I specifically want to avoid creating another account or making any changes to the existing production projects.

This is affecting access to an existing paid Hobby workspace and its production project. The original account remains accessible through my authenticated CLI session, but I cannot access the same account through the web dashboard. Could a Railway employee please review the account-access issue?