Review 360 links keep saving to another user's Private account, even after moving to a Team folder

I'm running into a Review 360 ownership issue that I can't shake, and I'm hoping someone here has seen it before.

Here's the setup: courses are built in Rise 360. One team member, our Reach Admin, was the original publisher of a course to Review 360, which put the item in their Private directory by default. Since then, I (a different user on the same Articulate 360 team) have made edits in Rise and generated new review links for updated versions of the course.

The problem: every new review link I generate still saves to the Reach Admin's Private account, not to my account or to a shared space. I can't update or replace the existing review link. My only option is to generate an entirely new link each time.

What I've already tried, and ruled out:

• Moved the Review 360 item into a Team folder.
• Confirmed I have Editor/Manager access on the actual Rise 360 course itself, not just the Review 360 folder.
• Confirmed I am publishing from the Rise 360 dashboard, not from inside Review 360.

None of that changed the behavior. New versions I publish still land somewhere outside my control instead of updating the existing Team item, and I still can't update the existing review link, only generate a brand new one.

A few specific questions:

• Is review link ownership tied permanently to whoever first published the item, even after it's moved to a Team folder and the correct Rise-level Editor/Manager access is in place?
• Is there a setting beyond course-level Editor/Manager access and folder access that needs to be changed, maybe on the Reach Admin's account or a team admin setting, to let another editor publish updates to the same item?
• Does this behave differently depending on whether we're all seatholders on the same Articulate 360 team versus separate team accounts?

For context: the person whose Private account this keeps saving to holds the Reach 360 admin role on our team, which is a separate permission system from Rise/Review 360. I checked and I don't have Reach 360 access myself, which just returns the standard "publish from your authoring app" message, so that appears to be unrelated to the Review 360 issue rather than the cause of it.

We're all on the same team subscription, so this doesn't seem to be a cross-team permissions issue. I've seen at least one other report of a collaborator with Manager-level access getting an incorrect or unrelated "publish new version" dropdown, so I'm wondering if this is a known bug rather than a permissions gap on my end. Any insight into what's actually controlling this, or a workaround for keeping one stable review link across multiple contributors, would be a huge help.

Thanks in advance.