Before jumping into the solution, I would ask clarifying questions such as:

Example: Is it stored in a table like USER_ROLE_ORG with columns: USER_ID, ROLE_ID, ORG_ID, IS_ACTIVE?

These questions help confirm assumptions and avoid designing the wrong solution.

Database Cleanup – Deactivating Third-Party Users

Assuming we have a table like:

USER_ROLE_ORG

USER_ID

ROLE_ID

ORG_ID

IS_ACTIVE

And ROLE_ID = 3 represents third-party users.

A simple solution is:

UPDATE USER_ROLE_ORG

SET IS_ACTIVE = 0

WHERE ROLE_ID = 3;

But this has issues:

I would design a stored procedure with the following steps:

This covers database-level cleanup with full traceability.

Appian-Side Cleanup — Removing Users From Third-Party Groups

After DB deactivation, we still need to remove the users from Appian Groups.

Easy approach create an MNI that loops through 10,000 users.This will create 10,000 instances → massive load → difficult to track failures.

Batch Removal Using Sub-Process

Create an expression rule that fetches only users with IS_COMPLETED = 0 from audit.
Use a Process Model with:
Batch size (e.g., 100 users at a time)
Loop or recursive chaining until all users are processed

High-Level PM Flow:

This produces:

Interviewers do not expect a perfect solution.

They check your ability to:

As long as your logic is structured and scalable, you will stand out.