Dynamic rules Tenants
Cross-tenant Dynamic Rules
Automations can be configured in the Shared Space. You can create conditions and actions using Programs, Certifications, and Organisation structures that are defined in Shared space, as well as courses, cohorts, and certificates that are shared, that is they do not belong to any tenant's category. When creating a rule in the Shared Space, only relevant conditions and actions are available. The usage of non-shared entities will be added in the future versions.
Cross-tenant rules are created in the Shared Space, like any other shared entity. Shared rules will be shown in the Dynamic Rules interface in all tenants, with a Shared Space badge. These rules can be only edited, enabled, disabled, or archived in Shared Space.
When tenant conditions (Users allocated to tenant or Users not allocated to tenant) or actions (Allocate to tenant) are configured in a dynamic rule in Shared Space, the tenant name will be hidden for users (usually tenant admins) who are not member of that selected tenant.

Dynamic rules and secondary tenants
Conditions in dynamic rules treat secondary-tenant memberships in the same way as main-tenant memberships, that is, conditions also match users who are only secondary members of the rule's tenant. This is likely to change in the nea future.
For example, a user's main membership is Tenant M and its secondary membership is Tenant S, The "Users allocated to tenant" condition in a dynamic rules in Tenant S will trigger for the user. The same holds true if the user has been allocated to a program on Tenant S and the condition "Users allocated to program" is applied.
For example, if a user’s main membership is in Tenant M and they have a secondary membership in Tenant S, the Users allocated to tenant condition in a dynamic rule in Tenant S will trigger for that user. The same applies if the user is allocated to a program in Tenant S and the dynamic rule uses the Users allocated to program condition.