Overview
The EasyLife 365 Admin serves as your administrative interface, empowering you to configure EasyLife’s functionality and tailor its components to suit your organization's needs. Designed for IT Professionals and Service Managers, this web application offers comprehensive control over EasyLife 365 Collaboration within your organization.
By default, once you activate EasyLife 365 in your organization, all users gain access to EasyLife 365 Admin. However, you can customize access by configuring Entra ID accordingly, restricting it to designated users if necessary.
Please note that access to the Admin interface is automatically enabled for all users upon onboarding. To maintain security, ensure you have restricted access to the Admin interfaces.
Within EasyLife 365 Admin, you can:
- Manage templates
- Manage policies
- Manage groups, guest accounts, and SharePoint sites
- Configure EasyLife 365 Collaboration settings
Compliance panels
Every Manage section — Groups, Guest accounts, SharePoint sites and OneDrive sites — offers a Details panel for a selected resource. That panel contains a Compliance section listing each governance rule and whether the resource meets it.
The section lists only the rules that are actually being evaluated. A rule appears when all three of the following are true:
- The policy assigned to the resource configures that rule. A rule the assigned policy does not define is not measured, so it is not listed.
- The rule still runs for the resource's current state. An archived resource shows only the archival review — archiving stops every other rule.
- The engine has recorded a state for the rule on that resource.
When none of the rules qualify, the Compliance section is not drawn at all.
An archived resource keeps the recorded values of its other rules. The engine freezes them for a grace period before clearing them, so an archive undone by mistake resumes where it left off. They are kept as data, not shown as rules, because nothing is measuring them — and the overall compliance verdict already ignores them.
If the assigned policy cannot be loaded, the panel falls back to listing every rule with a recorded state. A failed request must never hide a genuine non-compliance.