Overview
As an Admin, it's important to understand how archived modules will appear in the portal and how they affect device groups and classes. This article explains what you can expect when a module is archived or unarchived.
Key Points
- Archived modules cannot be assigned to a device group.
- Classes that were associated with the archived module are automatically archived.
- Performance analytics will remain available for archived modules.
- Archiving has replaced the ability to disable a module
- Only Moth+Flame Super Admins can archive or unarchive a module.
Q+A
What does "archiving" or "unarchiving" a module mean?
Q: What happens when a module is archived?
A: When a module is archived, it becomes inactive for a given organization. It is hidden from the device management page and cannot be used by devices. The associated class is also archived, and only Super Admins can see and manage archived modules.
Q: Can archived modules be assigned to a device group?
A: No, archived modules cannot be assigned to a device group. They do not appear in the list of available modules for selection.
Q: How does archiving affect classes?
A: When a module is archived, the associated class is also archived. This means the class will show as archived on the class page and will not be active.
Q: What does it mean to unarchive a module?
A: Unarchiving a module restores its active status. The module will reappear on the device management page, and the associated class will be restored and shown as active on the class page.
Why might a module be archived?
Q: Why archive a module?
A: Archiving unused modules keeps an organization tidy and focused on active learning needs. Archiving a module could be either temporary or permanent in nature.
Temporary use case: Learners who use magic links with mobile devices have the ability to see all modules within their organization. Archiving modules allows Admins to prune content so that specific training is available to Learners during a given time frame (e.g. during a launch event).
- Permanent: If an organization no longer has a subscription that includes an experience they previously had access to, the module will be archived and the data will remain available to Administrators.
How do archived modules appear?
Q: Can Admins see archived modules?
A: No, Admins cannot see archived modules. Only Super Admins have the ability to view and manage archived modules.
Q: How will archived modules appear in device groups?
A: If a module was assigned to a device group before being archived, it will appear grayed out within that device group. This indicates that the module is archived and inactive. Grayed-out modules can only be removed from the device group but cannot be used or interacted with.
Q: What happens to previously disabled modules?
A: Modules can no longer be disabled. Any modules that were previously disabled have been removed from device groups entirely.
Q: How does unarchiving affect device groups?
A: When a module is unarchived, it becomes active again in the device groups where it was previously assigned. Devices in these groups will be able to access and use the module once more.
Q: How do I see performance analytics for an archived module?
A: Performance analytics will still be available to Administrators even after a module has been archived. Admins can view analytics one of two ways:
- Unarchive a class associated with the archived module and viewing its performance page.
- View the performance page of an active class. Then use the module filter at the top left of the filter panel to select the archived module's name.
Q: Can archived modules be added to device groups?
A: No, archived modules cannot be added to device groups because they do not show up in the list of available modules to choose from.
Q: Who can archive or unarchive a module?
A: Only Moth+Flame Super Admins have permission to archive or unarchive a module for an organization.
For further assistance or if you have more questions, please don't hesitate to contact your Customer Success Manager or our support team.