Skip to main content
Version: 2.700.0

Ownership

In the Ownership section of the guest account policy, you can fine-tune the settings for managing ownerless guests and ensuring a minimum number of owners.

Ownerless Guest Policy​

The EasyLife 365 Collaboration Engine enforces this policy when a guest account is detected without an assigned owner. To manage such cases efficiently, you can enable Auto Heal—a mechanism that attempts to automatically assign an owner to the orphaned guest account. In case Auto Heal fails, you can define escalation measures, such as sending notifications or triggering webhooks.

Auto Heal Resolution Logic​

Auto Heal follows a strict fallback logic to determine ownership:

  1. Sponsoring Fields The primary source used by Auto Heal is the guest account sponsoring fields. If any sponsor-related information is available here (e.g., who invited the guest or was responsible for the account), Auto Heal will assign the identified user as the owner.

  2. Group Membership If no suitable user is found in the sponsoring fields, Auto Heal will then attempt to assign an owner based on group membership if selected. It evaluates the groups the guest belongs to and selects an appropriate group owner.

Ownership Policy Details

Minimum Owners Policy​

You can configure up to five owners for each guest account, ensuring that every account maintains the number of owners you specify. If an account falls below this threshold, the existing owner(s) will be notified and prompted to assign additional owners. You can customize the number of reminder notifications and define the action to take if there’s no response within the set timeframe—either disable the account or take no action (none).

Sponsorship Synchronization​

Starting August 1st, 2025, the sponsor field in Entra ID for guest accounts will be synchronized one-way with the schema data maintained by EasyLife. This means the values defined in our internal owners schema will be automatically pushed to and overwrite the sponsor field in Entra ID. The synchronization currently supports user objects only. If no corresponding owner entries are found in our system, we will attempt to auto-heal by pulling the sponsor data from Entra ID back into our schema extension.