Is there a way to remove all members from all projects?

[Samuel_Michaels2]

I would like to remove all members from all our projects and change the access settings to “everyone in my organization can find and access this project” and make my organization the project admin.

This would save me a whole lot of time, because we are restructuring our notifications across our organization.

Maybe there is a way to do this with Supersana or Make?

[Stephen_Li]

I’m not aware of a way to do this natively (and I’m not too familiar with Supersana, but the founder @Bryan_TeamKickstart is very active in this forum so perhaps he can weigh in). If you use Make, you could set this up (although I’m not sure if the pre-built modules support all of this or if you’d need to use the custom HTTP module). The basic logic would be:

1. GET all projects (or, if you have a list of specific projects, just grab their IDs and feed them into make in either a data store or some other input format)
2. PUT update each project to be public to org
3. GET all memberships for each project
4. Iterate through each membership and DELETE it

That said, is there a reason you want to remove everyone (instead of just leaving them and changing the privacy setting)?

[Bryan_TeamKickstart]

Thanks @Stephen_Li for the @mention so I could jump in to maybe help.

@Samuel_Michaels2 - Supersana can’t do this right now, but we’ve been debating bulk actions for adding and removing members, though we hadn’t considered the “Remove all members (except me)” use case. Interesting!

So, in short, if this is something you need to do right away, doing it in Make or Zapier is going to be the easiest and fastest way.

But, if this is not something you need right away, I’d like to hear more about the specific use case and this might be a good time for us to go ahead and develop it. We’re about 2 months backlogged on customer-requested feature development right now. So, if we decided to do it, it wouldn’t be for a while, just to set proper expectations.

Let me know if that would still be helpful and we can spec the details to fit your use case. (e.g. all projects, all projects on a specific team, all projects in a portfolio, etc.)

[Samuel_Michaels2]

We have around 200 projects which are identical in structure. We have different teams working on the projects at different times during the life cycle.

Atm we have around 15 people assigned to each project.

By removing them, I want to decrease the clutter in email notifications.

This way only people that assignees or collaborators will be notified on changes in the projects

[Samuel_Michaels2]

Hey Bryan,

unfortunately we need to do this ASAP

[Emily_Roman]

Hi @Samuel_Michaels2, as a workaround, you could try removing the members from the team the projects where created When you remove a user from a team, there is an option to remove them automatically from all projects too:

I understand this would need to be done manually and can take time but it’s one option you could try to make this process faster, instead of removing them project by project!