Skip to content
Ownership transfer acceptance fails with “Not Authorized
mnona88
OP

a month ago

Both the source and destination workspaces have active Hobby subscriptions.

The current owner initiated Transfer Ownership to a user who had already joined the project as a Viewer.

The recipient opened the transfer confirmation while logged into the correct account, clicked Confirm, selected their workspace, and clicked Transfer project. The final step returned “Not Authorized”.

The project remains in the original workspace, and Confirm is still displayed.

Does the recipient need Editor permissions to accept ownership? The documentation only specifies project membership.

Please advise how to complete the transfer safely. This project contains a production MySQL database. We have not changed permissions or reissued the transfer.

If account or project identifiers are needed, please provide a private support channel.

image.png

$10 Bounty

2 Replies

Status changed to Awaiting Railway Response Railway • about 2 months ago


Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 2 months ago


mnona88
OP

a month ago

Thank you. Before changing permissions on this production project, could Railway staff confirm:

  1. Is promoting the recipient to Owner a supported prerequisite, or does that action itself initiate an ownership transfer? The documentation only requires the recipient to be a project member.

  2. The acceptance screen explicitly says the recipient will be billed for the entire billing cycle, including usage before today. Your reply says billing starts from the transfer onward. Which applies to this transfer?

The recipient already owns the destination workspace. Please confirm the supported next step for the pending transfer before we change roles, remove members, or reissue it.


douglasluyinda

a month ago

Hi there!

The "Not Authorized" error during project transfer acceptance usually occurs due to workspace-level permission scope mismatches or subscription tier validation checks when binding billing to the destination workspace. 

Here is how to resolve this safely without impacting your production MySQL database:

  1. Root Cause Breakdown

Destination Workspace Permissions: To accept a project transfer, the recipient must have Admin or Owner permissions on the target workspace where the project is moving, as accepting the transfer binds billing and resource management to that workspace. If the user is only a member or viewer in the destination workspace, the API authorization check fails. 

Hobby Tier Constraints: Since both workspaces are on Hobby subscriptions, verify that the destination workspace has not exceeded its resource or project limits, which can block incoming project transfers.

  1. Step-by-Step Resolution
  2. Verify Destination Workspace Role: Ensure the recipient is an Admin or Owner of the destination workspace in Workspace Settings > Members.
  3. Cancel Pending Transfer: Have the current owner go to Project Settings > Members and cancel the current pending transfer. 
  4. Re-issue Transfer: Re-initiate the project transfer to the recipient user.
  5. Accept as Workspace Admin: Have the recipient open the fresh link, select the destination workspace (where they hold Admin rights), and complete the transfer. 
  6. Database Safety & Billing Clarification

Database Safety: Transferring a project does not restart, redeploy, or affect running services (such as your production MySQL database). It only updates project metadata and billing ownership.

Billing Cycle: As noted in the confirmation prompt, the destination workspace assumes billing for the active billing cycle.

Official References

Railway Docs: Project Transfers

Railway Docs: Workspaces & Roles

Disclosure: I used AI assistance to help prepare this response and reviewed the technical reasoning before submitting.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...