@RamprasadM1091 ⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Why Bell Notifications Fail Across Applications

When Bell notifications don't work across applications with different access groups, it's typically because of three main factors:

1. Access Permissions: Users in different access groups may not have the necessary permissions to receive notifications from other applications.
2. Application Context: Even though your notification rules are in the Org level ruleset, they might not be inheriting the proper context required for cross-application communication.
3. Notification Channel Configuration: The web gadget section rule might need additional configuration to display notifications from other applications.

Solution: Step-by-Step Configuration

Here's how to configure your Bell notifications to work across applications with different access groups:

1. Review and Update Access Group Settings

Make sure both access groups have the correct permissions:

• Navigate to Configure > Application > Access Groups
• Select the access group that's not receiving notifications
• In the Security tab, ensure they have permissions to receive notifications
• Check if the access group has the necessary roles to view notifications from other applications

2. Configure Notification Rule for Cross-Application Delivery

Your notification rule needs specific settings for cross-application delivery:

• Open your notification rule (already in the Org level ruleset)
• Go to the Channels tab
• Make sure Web Gadget is selected as a delivery channel
• Under advanced settings, explicitly select "Make available to all applications" to ensure cross-application visibility

3. Configure Web Gadget Section Rule

The web gadget section rule needs configuration to display notifications from other applications:

• Open the web gadget section rule
• Make sure the "Source" is set to "All relevant applications" rather than just the current application
• Check the section security settings to ensure it can access data from other applications

4. Update Application Settings

In each application involved:

• Navigate to Application > Definition
• In the Cross-Application settings, ensure that notification sharing is enabled with the other application
• Add the other application to the "Allowed Applications" list if not already present

5. Testing

After making these changes:

• Create a test notification in your application
• Verify the notification appears for users in the other application's access group
• If issues persist, check the system logs for specific errors related to notifications

Best Practices

• Use descriptive names in your notification rules to easily identify their source application
• Consider creating a central notification configuration if you frequently need cross-application notifications
• For complex notification needs, consider using a custom activity to handle the notification logic

References: Managing User Access with Access Groups Dashboard Configuration Configuring Advanced Settings for Access Groups