Explicit owner maintained in external source system
Some customers choose to maintain ownerships in an authoritative source system, such as an HR system to maintain managers for departments.
These are imported via the data import, and afterward "exported" to Omada Identity via the Warehouse to Portal mappings. This is done via the property Explicit owner.
With the Horizons feature enabled, the behavior of Warehouse to Portal mappings has changed, for more information, go to Migrating to Horizons documentation.
It is important that the explicit owner is only set via the ODW import from an external source system. If you update the Explicit owner property directly in Omada Identity, then the ownership synchronization will not import those owners to the Data Warehouse, and the access to owned objects in the Data Warehouse reports will be incorrect. If you want to use a property to update owners, you can instead use the property Manual owner.
Adding owners via a source system
Here Robert Wolf has been added to the property Managed by for an Active Directory Group.
After a data import from Active Directory, Robert Wolf have an additional assignment as Explicit owner for the group.
Removing explicit owners
If the Managed By property is updated in the source system (Active Directory in this example), then the owner is removed from the resource on the next import.