Mark Separation For a Stakeholder
Qapita provides a streamlined process to mark the separation of an active individual stakeholder due to various reasons such as resignation, termination, death, or retirement. This ensures accurate record-keeping and proper account management within the platform.
Steps to Mark Separation:
- Access the Stakeholder Page:
Begin by clicking on Stakeholders in the menu located on the left side of your screen. This will navigate you to the comprehensive list of all stakeholders.
- Navigate and Select Mark Separation:
Locate the specific stakeholder for whom you wish to mark separation. Click on their entry, and then select the Mark Separation option. The "Mark Separation" screen will be displayed.
- Select the Date of Separation:
On the "Mark Separation" screen, choose the precise Date of Separation using the provided date selector.
- Select the Reason for Separation:
From the dropdown menu, select the appropriate Reason for Separation that applies to the stakeholder.
- Deactivate a User Account (Optional):
If you need to deactivate the user's account upon their separation:
- Click the Deactivate User Account button.
- Type the stakeholder's Personal Email ID to confirm the deactivation.
- Transfer a User Account to Personal Email (Optional):
To transfer the user's account to a personal email ID without deactivating it:
- Click on Manage Account.
- Then, click Transfer Account to Personal Email. This action will trigger an invite email to the user’s personal email ID, transferring their account ownership.
- Type the Personal Email ID for the transfer.
Complete the Process:
Finally, click the Mark Separation button to finalize and complete the process. Once updated, the status of the stakeholder will automatically change to inactive.
Note: Marking a stakeholder as separated updates their status to inactive, ensuring all related records reflect their current standing within the organization.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article