---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# General guidelines

# General guidelines for activity stream {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Consider these general guidelines when configuring your activity stream.
Note:  
For design considerations and user experience general guidelines when configuring your activity stream, refer to the [Activity stream screen section](https://horizon.servicenow.com/native-mobile/screens/activity-stream-screen) in the [Horizon design system](https://horizon.servicenow.com/native-mobile/overview) website.

Add activity stream as a stream segment
:   Depending on your requirements, you can add an activity stream as a screen segment in a record screen or have it as a standalone screen.

Include in incidents and requests
:   Incidents and requests that have pending activity should include an activity stream screen segment.

Use of update history
:   Use an activity stream screen segment for records where history updates are important. However, if you're looking at a user profile record, activity stream segments may not be needed.

Rename for user familiarity
:   The term Activity stream as a tab name may not be understood by some users. Consider renaming this tab to a term your users are familiar with, such as Updates, History, or Notes.

@mention feature
:
    * Users can @mention someone in the activity stream, and the mentioned user will receive an email and push notifications based on admin and user preferences. For more information, see [Mobile push notifications](https://servicenow-prod.fluidtopics.net/fdREAsmUEOS4AYORiulw3A "Mobile push notifications are configurable pushed messages that appear directly in a mobile app. These push notifications are non-actionable or actionable, and are configured by administrators to meet the needs of their users.").
    * Supporting @mention mobile push notifications requires configuration and isn't supported by default for all tables. In this case, consider adding support for tables which require collaboration between users to increase communication efficiency.
    {#configure-activity-stream-guidelines__ul_a3n_g3d_kfc}

User role user or user criteria permissions
:   You can restrict access to the activity stream segment within the Record screen for specific users by assigning user roles or user criteria permissions. For more information, see [User roles and user criteria permissions for mobile apps](https://servicenow-prod.fluidtopics.net/Hs6qtB0ptBxSXe~1qRKlng "User roles and user criteria permissions are access control mechanisms that enable you to define roles or segment users into groups within the mobile platform. With these permissions, you can show or hide different components of your mobile app to either individuals or groups.").