What project hierarchy do you use in RedMine?

Question

Redmine

Hello guys,
now we are going to introduce RedMine into the development process and we want to give access to our clients (not to everyone, but one account per client company). And we need to make sure that our tickets are not visible to customers.
The question arises how to organize everything correctly and use all the features of RedMine.
Here is the first option that came to mind. Each company has its own folders for each project, but how do developers not get confused in all this and will have access to all questions in one place, and not separate questions for all projects.

• Internal support
  • ProjectName #1
    
  • ProjectName #2
    
  • ProjectName #3
    
  
  
• External support
  • Company 1
    • ProjectName #1
      
    • ProjectName #2
      
    
    
  • Company 2
    • ProjectName #1
      
    • ProjectName #2
      
    
    
  
  

Well, here is the second option in which there is just a list of projects and that's it, everyone has access to the same projects but see different things, users do not see those tickets that were created within the company, they see only those tickets that were created by the "Users" group

• ProjectName #1
  
• ProjectName #2
  
• ProjectName #3
  

Answer 1

Both options are viable, so that developers do not get confused between projects, it is necessary to switch to cross-project requests. That is, set up a request for tasks not within the project, but for all projects, and you will be happy. Alternatively, you can add cross-project versions, install the Clear Plan plugin and let the developers work within the framework of the versioned work plan