This article explains the different methods available to trigger the archive workflow. Regardless of the method used, the process initiates the offboarding rules you have configured via CloudM Automate, ensuring Email, Drive, and Chat data is archived.
Please note:
- Supported Features: Please review the Supported Features and Exclusions to understand exactly what data is archived (e.g. Chat limitations, Shared Drive exclusions).
- Limits: Ensure you are within the Fair Use Policy limits (maximum 5 archives per User ID).
Triggering the Archive Workflow
While the goal is to archive user data, the mechanism used in CloudM Automate is the Offboarding Workflow. There are three primary ways to trigger this workflow:
- Manual Trigger: Initiating the archive process for a specific user directly from their profile or the user list.
- Automatic Trigger: Configuring the archive to start automatically based on specific events, such as when a user is Suspended or Moved to a specific Organizational Unit (OU).
-
Bulk Trigger: Using a CSV import or bulk selection to trigger the archive for multiple users simultaneously.
(Note: For large scale migrations or bucket imports, please see the Large Volume Archiving section below).
For detailed instructions on how to configure and execute each of these methods, please refer to the guide below:
Verification: Once the workflow is triggered and complete, you can verify the archive results by navigating to Archive > Archive Status.
Large Volume Archiving & Migrations
If you are planning on archiving a significant volume of users (e.g. migrating legacy data or Importing users migrated to a different Cloud Storage bucket), we recommend reviewing the Data Import process.
This method is optimized for handling large-scale ingestion from CloudM Migrate rather than triggering individual offboarding workflows.
How to import users migrated to a different Cloud Storage bucket