Changing Project Ownership Defaults to Manage Access

[#1]

it comes as a great surprise to us that changing the Owner of a project does not automatically give that person manage access to the project.

Seems kinda odd you'd want a view-only Owner of a project.

So hoping to get some traction around making Manage the default, or perhaps an option in preferences so I don't remove someone else's preference for current behavior.

[#2]

Hey Kevin,

When I create a new project, then change the owner, it does give them manage access. Maybe this is a setting somewhere? I couldn't find it but maybe someone at Workfront could chime in here?

[#3]

It's possible it's a side-effect of Inherited Permissions (our planners have view-only access to all projects by default).

Still, if a view-only planner is given Ownership of a project, it still makes sense to me to boost that user to Manage automatically. So maybe that's an edge case they didn't consider.

[#4]

@Kevin — could you explain your situation in more detail? I'm wondering about the "our planners have view-only access to all projects by default" comment you made which would seem to contradict having "manage" ownership over the project. As you know, there are inherited permissions and access levels. Say your planners were limited to "edit" access only, they would not be able to be given "manage" afterward, which makes me think that this could potentially be a bug as well. If so, I would suggest logging the potential bug here so that we can look deeper into this: https://one.workfront.com/s/support. Thanks!

[#5]

@Jeremy Flores

By default, all our planners have view-only access to all other planners' within the same Company, via the Portfolio.

However, if a current project Owner designates a new project Owner, it was our assumption that the new Owner would get Manage permissions (i.e., the system should elevate any pre-existing access).

It caught us off-guard that the new owner would retain their old view-only access, basically meaning they were owners in name only; they couldn't actually do anything.

In our mind, being an owner of a project should automatically grant the access necessary to carry out ownership duties; which necessitates Manage access.

[#6]

Thanks @Kevin. The access should be elevating. There has to be something more specific in your case. We checked on our side and it does change the new owner's access to manage even though there is inherited access from the portfolio (similar to what Sarah described below in her instance). The only consideration would be if the user making the change doesn't have the manage access to give in the first place, but then how does this user make the change?! Can you please submit a ticket so that we can look deeper into this? Once you've submitted one, let me know so that I can close this idea out. Perhaps we will end up with some specific case that isn't covered, but based on what you are currently describing...this sounds like a bug.

[#7]

Unfortunately, I put this in as a ticket and it was closed as "working as intended" (essentially): 00222932.

We just went through some small amount of effort to create documentation sending planners through a 2-step process to change ownership as a result.

So further testing my be difficult.

[#8]

Hi Kevin, I am marking this delivered as this seems like a bug. We have opened a new incident for this: 00226940. Thank you.

[#9]

Hi,

I'm looking for the option to manage Project owner access associated to a particular project. Please let me know the procedure to do updates.

Thanks