Skip to main content
12-Amethyst
October 3, 2025
Question

cross project tracker references and user management

  • October 3, 2025
  • 1 reply
  • 438 views

Hello community,

Is there a way to share users across multiple projects?

We have several projects where trackers are connected via reference fields. However, if a user is not a member of both the source and target projects, they either cannot see the referenced items or encounter errors when editing trackers — even in the project where they do have access.

Ideally, we would like to avoid manually managing the same users across multiple projects. While we understand that not all users should have access to every connected project, it would be acceptable if broader access is required for reference resolution to work properly.

Is there an option or configuration that allows tracker references to function regardless of project membership? I’ve looked through the settings but haven’t found a solution.

Thank you in advance for your help!

1 reply

13-Aquamarine
October 4, 2025

I'd suggest using User Groups.  Create a User Group, assign the appropriate users to it, and then assign that group to the appropriate roles in the appropriate projects.   Then if you want to give a new user that access to those projects, just add that new user to that group.

12-Amethyst
October 7, 2025

Hello Geoffrey,

thank you for your feedback!

Is there a way that Project owner can maintain this group?
Idea is to not provide to user "super user" nor "codebeamer administrator" privileges or access to another groups.

thank you

 

13-Aquamarine
October 7, 2025

I believe that currently there is a single permission "Group - Administrate" that lets you both add/remove members to groups and lets you assign repository permissions to that group.   Since assigning permissions to that group effectively lets you grant yourself whatever repository permissions you wish, you normally only give Group-Administrate permission to a system administrator.   Group permissions is not my focus area, so if anyone disagrees with anything I've written here, please post a correction.