From a management/maintainability perspective, this was a big issue when we adopted Asana and is becoming a bigger issue as we have tried to expand usage within our organization. There are numerous forum topics about this and most just say contact support…
The transferring ownership that seems to be the common case with others is probably our most common issue as well, but it also extends to (what should be) really simple maintenance items like fixing a project that was created under the wrong team or trying to support a coworker that needs help on their project.
Is there anything available at this point to have super admins automatically added as a project admin as a default on all new projects (even if the owner could go in and remove it). That would at least give us a starting point where someone would have to take action to get us into a bad state.
I agree. The model is clunky and I wish was more customizable or permissions to certain project aspects could be edited by a super admin. A lot of our PMs are frustrated when they go in to edit the project overview tab or move things across internal teams. I hate making things more complicated but at this point it seems like we need another permission tier.
Assuming you’re both on enterprise plans (based on the post title), have you tried the new work access mode? I think it offers a good solution for giving you (super admins) access/permission to all work without needing to have you added as a member (could mess with reporting/flood you with notifications, depending on your setup).
Now that team sharing on projects is a bit more robust, that’s another avenue (e.g., give certain teams admin access to projects). You could also play around with project templates (give certain people admin rights to projects created from a template); at scale, I think it makes sense for almost all projects to get created from templates.
