We're preparing to upgrade to 3.13 next week and through testing we've noticed that the Project Admin role doesn't include the 'transfer projects' function. We were hoping this role would allow some of our team to deal with requests from staff to move projects to different authors (usually happens when someone leaves their post but their Xerte projects are still in use). Is this a deliberate choice to restrict that role? And would it be much work to add?
Hi Yvonne
from memory yes I think this was a deliberate choice. e.g. the project admin role is for those who might help users with their projects but not have access to change of ownership and especially not bulk change of ownership which can easily go wrong if you aren't careful, and that's what you would typically use when someone has left their post.
So I think the project admin role (as it is now) is meant for helping users with their projects but not transfer of ownership.
I think at the moment transfer of ownership is meant to be far more restricted to those who have direct responsibility for that as it's not easily undone.
HTH
Ron
Onderwerp Auteur
