User Deprovisioning & Transferring of ownership

Hey Community,

As time goes on and new features are added to Asana, we need a better way to transfer items created by a user after leaving an Asana team or organization whether its voluntary or involuntary. it’s been easy to take advantage of using features such as goals, projects, rules, and more. @lpb provides a great resource as to what some of those are here.

My Request
It would be great if Asana could add additonal settings for when an employee leaves the company or team. Similar to what happens when someone leaves and a project is transferred to an admin, giving the ability to see all items owned by that user and having the ability to transfer anything necessary will be huge. This is crucial for companies and something such as this tends to be missed by IT teams if:

a) There’s Shadow IT at play and they don’t know the tool is being used within the org
b) the org doesn’t have SCIM provisioning set up or are not in a plan that includes it
c) An org doesn’t have an SSO provider

Potential Solution

  • Additional section within the Admin portal that gives you a breakdown of what is owned by each user by feature (e.g. rules, projects, etc.).
  • Ability to click on a user and see what is owned by them
  • Ability to pull a report and see who owns what
  • Ability to modify ownership items in bulk

Anything else I may have missed?

2 Likes

Voted!

Thanks, @AndySaavedra, for contributing this!

Larry

1 Like

Oh perfect thanks for creating this @AndySaavedra

I hope this will be implemented as it would be very helpful

1 Like

I am working on a tool I called “Offboarding report” giving you a list of objects owned by the person: projects, templates, custom fields, portfolios…

I think it will be useful!

2 Likes

Hoping this gets way more votes since the overall lack of admin/super-admin access, reporting, and controls is a huge pain point.

For example: We just lost edit access to a bunch of Templates (in the new format, if that matters) because edit access to them apparently needed to be manually transferred/shared by a leaving staff member before their account was offboarded.

There is bascially no IT/admin-level visibility into what is going to break during an offboarding (rules, integrations, template ownership, etc etc) and it becomes incumbent on other staff to discover and flag such things at which point it appears filing a support ticket is the only recourse to regain access?

At the very least one would hope Asana would want to take a load off their own support staff by making offboarding workflows more robust for their customers!

I am working on a tool to (partially) solve this. It is called “Offboarding report” and will be ran by a leaving employee (or their manager) to spit out a list of objects owned by them.

That’s great to hear, Bastien! I don’t think any of us considered a report that gives you the information as well. That would definitely be useful in situations where an audit needs to be performed on a large set of users.

1 Like

Is the tool that you are building through Flowsana or will that be a new tool that is created and gets added to the Marketplace?

Neither, it will be a webpage you visit to get the report.

1 Like

Definitely keep me posted regarding that tool! You rock @Bastien_Siebman :star_struck: