Search across content groups
The current community search gathers Members, Posts, Gigs, Events, Spaces, and Resources into ranked tabs. Results are limited and grouped so a query remains readable instead of becoming one unstructured list.
Search across eligible community content and return through one ordered stream of global and community activity.
People should not have to remember which tool contained a person, post, event, space, gig, or resource. Search groups the content the current member is allowed to see, while notifications preserve the source community and destination so activity can be reopened rather than merely announced.
The current community search gathers Members, Posts, Gigs, Events, Spaces, and Resources into ranked tabs. Results are limited and grouped so a query remains readable instead of becoming one unstructured list.
Search requests run through the existing content endpoints and membership context. The experience does not deliberately surface private destinations as a shortcut around their access rules.
Platform and community notifications retain community identity, activity title, message context, and a destination. Opening an unread item marks it read before moving to the appropriate profile, conversation, post, event, or community route.
Mark individual notifications read or unread, clear items, filter unread activity, or mark the current collection read. Live events keep the list and unread count synchronized where realtime delivery is active.
Supported browsers and installed experiences can expose push permission and device delivery preferences. The product clearly distinguishes Enabled, Blocked, Off, unavailable, and not-yet-configured states.
Enter a community query or open the relevant notifications collection.
Use grouped result tabs or time-based notification groups to understand the context.
Follow the selected result or notification to its exact source.
Clear search, manage read state, or configure supported push delivery for the current device.
Community, space, circle, Library, and membership access continue to shape what can be returned.
Notifications preserve community-aware paths so the member arrives in the correct shell and context.
Push delivery depends on browser support, configuration, permission, device token, and the member’s device preference.
Search and in-product notifications are part of the signed-in experience. Push delivery requires a supported device/browser, current configuration, user permission, and an active registration; it is not presented as guaranteed delivery.
The current search groups eligible Members, Posts, Gigs, Events, Spaces, and Resources. Individual tool directories can provide additional filters and deeper search.
Search uses the member’s current community and content access. It is not intended to bypass space, circle, Library, or membership permissions.
Yes. The current notification surfaces support individual read/unread actions along with mark-all-read behavior.
Push depends on service configuration, browser or installed-app support, permission, a registered device token, and the device-level delivery preference.