domain driven design - DDD: Storing reference to non-Aggregate Root Entity from different Bounded Context -

I am struggling to understand the model of my problem:

• A company There may be several teams.
• Each team should have a unique name per team.
• With a list of all reports for a company, a particular team should be able to retrieve the report.

Right now, I have 3 round contexts - company, team and report. I believe that I should go to the team to unite my unique name inside the company - though , As I think:

"There is nothing beyond all limits, if I can only reference an AR from my report AR, then I do not store that team Which can come under my report - just the company.

I It is thought that this team can be present in the form of BC and the company can also be within BC.One team is formed when the company is in the form of a unit within BC Here, Naming the team and irreversible enforcement can be ensured. Team BC still existed and the report can still retrieve the reference of TeamID from the report AR, however, this Team ID and team repetition both

Is this approach correct or am I missing something?

I am confused if I have 3 BC, which is 2E Should be of P., or the concept of a team unit inside company BC should be missing.

Maybe I am confusing Gautam relations I need a total route - I'm not sure!

Gulp, help!

In your example the company and the team can not have a contex connected, this unit (company or group) Aggregation can be root, it depends on work), identification of company identity, team name + team name identification is in the team.

Bound context is a combination of model, which should reflect the meaning of the selected subdomain Team and company can make a BC, Reporting is another reference.

If in your example reporting is just some information for easy display for the user, then there is no aggregation route in the context related to this reporting because there is no business logic and rule. Use simple DTO to display.