@TracyAllenUNB There have been some comments about making features Role based and allowing configuration of what each Role can and cannot do. It would be good to know that consideration is being given to this and that configuration could, for example, allow for project team members to to view all aspects (inc. the Timeline which I think is essential) but not edit/add - e.g:
- Typical Roles: Project Manager, PMO Officer, Project Workstream Lead, Project Team Member.
- The owner of a project could then be able to have a matrix of features against role and the intersection for each could define Add/Edit/View/Hidden.
- Add/Edit would require a Project licence and View should be included in E3/E5
This need to work in Named Organisations and not just Default Organisation as we find MS Partners only recommend Named Organisations.
Microsoft