We're unable to change account emails, swap linked GitHub accounts, or modify login credentials under any circumstances. This is a hard security boundary, not a policy limitation - performing these changes would compromise account security for all users.

The path forward is to recover access through your original auth provider. Since your account is linked to the "Medicals-Inc" GitHub account, you would need to regain access to that GitHub account (for example, by updating its primary email to your new domain through GitHub's account recovery process). Once you can log into that GitHub account again, you can log into Railway and update your settings yourself.

If the old email domain (medicals.inc) is part of a company domain migration you control, you may also be able to set up mail forwarding from the old domain to receive GitHub's recovery emails.

Thank you for answering to my quesiton.

I understood that and anyway I will check my ex-Git hub account again

I appriciade it

Hi Railway team,

This is Yuki Okawa.

Following up on this thread — the login migration to my new GitHub (Medicals-Group) and email (team@medicals.group) is done, but it left my GitHub deploy integration broken.

Auto-deploy now fails for my service with "No project member has access to this GitHub repository." Even though:

The Railway App is installed on org medicals-inc-dev (all repos) and my account is an Owner of that org.

But in Railway, the repo picker only shows repos from my old GitHub identity (MEDICALS-Inc), never medicals-inc-dev. The GraphQL githubRepos query returns "Not Authorized", and on GitHub the Railway App authorization for Medicals-Group shows "Never used."

It looks like the GitHub App / repo-access link wasn't migrated to my new GitHub identity when the login credentials were switched. Could you re-link the GitHub integration (installation for medicals-inc-dev) to my account/workspace?

Account: team@medicals.group (34475562-724e-45d5-900f-5b6fee638ff9)

Workspace: "medicals-inc's Projects" (1fa8cf4f-0375-408e-a201-de9d0470d4b6)

Project: airy-enchantment (065d8bb1-666b-4ce5-ae2a-4a9c7acfdc41)

Service: respectful-quietude (02ea7201-11ee-4409-9bc8-68aafe41b4d3)

Repo: medicals-inc-dev/medicals-system

Thanks!

Thanks for the detail. Logins on Railway are handled through external providers (GitHub, Google, or email), so we can't change credentials or re-link a GitHub identity to an account directly, and any change that affects account access has to start with confirming ownership of the account.

Before we can look into the GitHub integration for this workspace, could you verify ownership of the billing account by sharing the last 4 digits of the card on file, the amount and date of a recent invoice, and the billing name and address. Once that checks out we can direct your request to the right team to take it from there.

Thanks. There's no billing name or physical address on file for this account — the invoice only lists the email under "Bill to". Here are the ownership details I can provide:

Card on file (last 4 digits): 1663

Recent invoice: TBQCSLEG-0003 (Receipt 2348-8118), paid June 16, 2026, amount $5

"Bill to" on invoice: team@medicals.group / team@medicals.inc

Account email: team@medicals.group

Hopefully the invoice/receipt numbers plus card details are enough to confirm ownership. Once verified, please re-link the GitHub integration for workspace "medicals-inc's Projects" (1fa8cf4f-0375-408e-a201-de9d0470d4b6) so auto-deploy from medicals-inc-dev/medicals-system works. Thanks!

Thanks for sending the ownership details. We have the invoice, receipt, card last 4, and workspace information on the thread.

Because this request touches account identity and GitHub repository access, we still need to treat it as an account-security change rather than a normal GitHub integration reset. The next step is a human review of the ownership evidence and the requested GitHub installation/repository access before any re-linking can happen.

We have not made any account or GitHub identity changes yet. We will follow up here after the review.