At present, whenever a customer creates a new JWM TMP project and wishes to filter this project on another board with Sprints on it, they are required to set up new access permissions each time to manage Sprints, otherwise, the permissions will break since the new project doesn't have the permission and won't let users to manage it. This process could be significantly streamlined and improved if the Administrator access were automatically equipped with the 'Manage Sprints' function. Given that managing Sprints seems like an inherent part of the Administrator role, implementing this change would be highly beneficial and would enhance operational efficiency.