[✅ Solution] Will removing an individual from an organization break automations?

🙏 Ask the Community
1

2026-03-03_ (2)
2026-03-03_ (2)930×523 83.8 KB

I have two individuals that are assigned an item. Hypothetically, if I was to remove one of them from the organization or app, would that break the automation, or would the item simply be added to one individual instead of the two of them?

I had somebody leave the organization, and I want to make sure that I don’t accidentally break automations that we’re being assigned to them.

2

That is a very good question. I think the item will be added to one individual instead of two by the automation. The removed user should not appear in the automation anymore.

If you want, we can run a test on the Tape Partners workspace and see what happens. You can add me to a test workspace and then remove me from the workspace and see if that breaks the automation.

2 Likes
3

Great idea. I’ll look for my login for the partner space.

4

I had a similar instance where I had to add a guest into a member field. Two points here:

  1. You cannot normally add a guest into a member field via automation.
  2. @Jason had suggested me a code script earlier in one of the posts, and I used that to add a guest into a member field ID.

In this case, the automation definitely breaks because it is a hard-coded ID. I had to create an app which acts like a variable, and then these days all I have to do is switch the guest ID in that app and my automation does not break.

  • typed by wisper :smiley:
1 Like
5

I’m so glad that you’re enjoying Wispr. It’s a really cool program, isn’t it!

Thanks for the additional insight. I’ll definitely keep that in mind.

1 Like
6

In short - no.

@Luis and I did some testing and a task will still be assigned to the “ghost” user even after they are removed from an org.

I spoke with the Tape team and this is expected.
Here is the how/what/why.

[Tape] decided to avoid pruning all data / workflows when a member is removed, to avoid disruption and also allow a scenario where the user is readded → And all is as before.

However, users will not be able to add the removed member to user fields manually via the UI anymore, and also if you change the automation, remove the removed member, you cannot add them back.

This makes the system more resilient and preserves data, while still blocking the removed member from logging into the org. Admins can then decide whether they want to clean up the member, e.g. if they need to hand over assigned tasks to a new member instead via automations.

This is actually well thought out. Imagine if you removed someone from an org and they ‘disappeared’ from any automations. You would be left with orphaned items and have no way of knowing what that user was responsible for or what needed to be reasigned.

2 Likes