Adaptive Workflow for Deletion Requests
Organizations may be stuck in “Pending” status if their RDU was never signed, and there is no intention of the org profile becoming active. Examples may include: 1) duplicate org profiles accidentally being made, 2) an organization being dissolved in between IRIS onboarding and activation, 3) an organization onboarding with the intention of having multiple departmental profiles, and deciding to use one instead, etc.
These types of org profiles cannot be deactivated because their RDU was never signed, and deletion is impossible. Therefore, an adaptive workflow is necessary to reduce confusion, visual clutter and frustration for Local Leaders trying to audit user and organization access.
Note: Active organizations that no longer wish to be in IRIS must simply be deactivated, without altering their organization profile information.
In cases where the IRIS Team receives a request to delete an organization, IRIS Admin will implement the following solution:
- IRIS Coordinator Receives Request: The coordinator will discuss the request with local leaders, ensuring the profile is unwanted and will not become active.
- IRIS Coordinator Relays Request to IRIS Admin: The coordinator will inform IRIS Admin of the request and specify exactly the organization in question.
- IRIS Admin “Bleaches” the Organization Profile: An admin will modify the duplicate/pending organization by clearing all information associating the organization with that profile.
- IRIS Admin Renames the Organization Profile
- Use the following naming convention: z_DO NOT USE
- This is for the purpose of clearly differentiating these “deleted” organizations, and to put them at the bottom of data exports.
- IRIS Admin signs RDU. To bring the organization out of pending status, IRIS Admin will assign themselves as RDU Contact and sign the RDU. The organization will temporarily become active.
- IRIS Admin immediately deactivates the organization.
Need help? IRIS Support | Last updated: May 22, 2025