data structures – How to avoid redundancies with modified database for different projects?

I have a project where I need to synchronize data between a management system and a controller.
The management system has additional data that the controller does not need, such as the name of a user, as well as additional ways to structure the data such as UserGroups in the example below.
Is there a best practice to structure the data in a way that avoids redundancy and has the data needed in each project?
I was thinking of a data structure like the following but am not sure if I might run into problems later.

DB Structure