Is there any way our team can keep our projects somewhat separate but still allow access. In our environment, we have a large-ish group whose constituents all work with data but the team has started treating their individual programs as projects which doesn't seem correct. These would be projects that never end 🤔. I think what we really want is to have some way of keeping our projects separate from other programs. The idea isn't to limit access to them but is there a grouping above the level of a "Project" that can be used to group projects together in a hierarchy.
Programs are like "Data Management", "Data Practices", "Data Governance", "Data Operations" and each have their own projects. Is there any way for us to work within a hierarchy above the level of "Project".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.