Tenant-Specific Inbox Notifications in AEMaaCS

[tejaswi_aem]

We have a multi-tenant setup in Adobe Experience Manager as a Cloud Service (AEMaaCS) with four tenants. One of our clients, who is an admin in the PROD environment, is currently receiving inbox notifications for all four tenants. However, the client wants to receive notifications only for their specific tenant/project. We have tried updating our client permissions from AEM Admin to our project specific admin group that has resulted in receiving only assigned notifications, that is notifications with his name only.

Requirement: Configure inbox notifications to be tenant-specific, so the client receives notifications only for their assigned project/tenant.
Expected Outcome: The client should receive notifications only for their respective tenant, reducing noise and improving notification relevance.

Please let me know if there is option to create tenant specific inbox notifications groups in AEMasCS.

[arunpatidar]

Hi @tejaswi_aem 

I am not sure if you can customize the OOTB inbox. In our use case we build the custom Shell page to show workflow notification as per tenant/site.

You can also try to build a custom dashboard/inbox page with tenant > site > dashboard navigation and control the access as per use case.

[ButhpurKiran · Accepted solution]

Admin client could be added as a member of a high-level admin group (likely with administrators or workflow-administrators roles), and that group has visibility across all tenants/projects.

For receiving inbox notifications only for their specific tenant in AEM as a Cloud Service, create a separate admin groups for each tenant (e.g., tenantA-admins, tenantB-admins) and assign only the relevant users to these groups. Make sure to remove broad admin roles like "administrators" or "workflow-administrators" from users who shouldn't access multiple tenants, so their inbox shows only tenant-specific tasks and workflows. Then, structure workflows and task assignments so they are limited to the appropriate tenant groups or users, and avoid assigning them to global admin groups that span all tenants. Optionally, we can personalise our inbox view using the Inbox Search Rail feature to filter results by workflow title, tenant, or project, though this is just a visual preference and not a secure way to restrict access.

Thanks