Archiving SaaS apps
You can archive apps that are not being reported in browser events, which will hide them from the app inventory and exports by default to ensure only relevant apps are shown for analysis. (For more information on exporting, see Exporting SaaS apps.)
For ease, you can automatically archive apps that do not report activity within a specified time frame. Additionally, you can manually archive apps individually or in bulk. When an app is archived via either of these methods, subsequent app activity reported in a browser event will cause it to automatically transition to an active state.
Each app will have one of four states:
| State | Description | ||
|---|---|---|---|
| Active |
The app has been reported in browser activity. This is the default state of apps that are automatically added to the inventory. The app can be manually or automatically archived. |
||
| Archived |
The app was automatically or manually archived. If the app reports activity, it will automatically transition to an Active state. |
||
| Always archived |
The app is in a permanently archived state, meaning it cannot be auto-unarchived by new browser activity. The app can only be manually unarchived.
|
||
| Always active |
The app was manually unarchived and is now permanently active, meaning it cannot be auto-archived. This is the default state of apps that are manually added to the inventory. The app can only be manually archived. |
For instructions on how to manually or automatically archive and unarchive apps, see:
- Manually archiving and unarchiving SaaS apps
- Auto-archiving SaaS apps in the FortiDLP Administration Guide.