# User Segments

### Overview

User Segments in MangoApps allow admins to create collections of users based on predefined rules (dynamic collection) or manually selected users (static collection). These segments can include network users, guest users, or a mix of both. Admins have control over who can utilize the user segments, such as domain admins or both domain and intranet admins.

<figure><img src="/files/sOB1wfHEUkNbCk721YR2" alt="" width="563"><figcaption></figcaption></figure>

***

### Use Cases for User Segments

#### **Targeted Messaging**

Send announcements or updates to specific groups of users without creating a group or channel.

Notify **highly engaged users** about new features or opportunities.

Reach **not engaged users** with re-engagement campaigns or surveys.

#### **Personalized Navigation & Branding**

Customize the platform experience for different user groups (e.g., employees vs. external partners).

Provide role-based navigation menus that highlight relevant tools and resources.

#### **Automated User Management**

Dynamically assign users to segments based on their department, job title, or location.

Maintain updated user groups without manual intervention.

#### **Automate Onboarding & Training Assignment**

Create a segment for **new hires** and send them onboarding materials automatically.

Assign training resources based on job roles or geographic location.

***

### Auto-Generated User Segments Based on Engagement

MangoApps automatically generates user segments based on user engagement levels, updating them every 30 days. These segments include:

* Highly Engaged Users
* Engaged Users
* Moderately Engaged Users
* Not Engaged Users

{% hint style="danger" %}
These user segments **cannot** be deleted nor edited.
{% endhint %}

***

### Segment List Dashboard

The Segment List Dashboard provides an overview of all created user segments, including:

**Name:** Unique identifier for the segment.

**Category:** Type of users included (network, guest, or mixed).

**Type:**

* **Rule Based:** Created using predefined conditions such as job function, location, or custom attributes. Membership updates dynamically based on attribute changes.
* **Specific Users:** Created by manually selecting users; membership remains fixed unless modified by an admin.

**Count:** Number of users in the segment (refreshable by clicking the Refresh icon).

**Created By:** Displays the admin who created the segment.

**Last Updated:** Date when the segment was last modified.

**Actions:** Admins can edit, duplicate, or delete segments.

<figure><img src="/files/qxaqdsVJdczarv934oJp" alt="" width="183"><figcaption></figcaption></figure>

***

### Creating a New User Segment

Navigate to **Users > User Segment** and click **New Segment**.

<img src="/files/NaAG8VlXutAMxnDLZdiE" alt="" width="563">

Enter a **name** for the segment.

Choose a **category**:

* **Network User:** Only includes network users, used for user-segment-based branding.
* **Guest User:** Only includes guest users, used for user-segment-based navigation.
* **Mixed:** Includes both network and guest users but cannot be used for user-segment-based navigation.

Select a **type**:

* **Specific Users (Static):** Manually add/remove users; membership remains fixed.
* **Rule-Based (Dynamic):** Users are automatically added/removed based on profile-based rules.

Select the users or define the rules and click **Save Segment**.

Click **Cancel** to exit without saving.

***

### Rule Based User Segment Type

When you use multiple conditions with the **same** field, such as "location = ..." and "location = ..." repeated several times, the logical operator employed is '**OR**.' Essentially, it will translate to "location = ..." **OR** "location = ...".&#x20;

On the other hand, when you utilize multiple conditions with **different** fields, e.g. "location = ..." and "title = ...", the operator is '**AND**.' For instance, "location = ..." **AND** "title = ..."

Here's another example to illustrate this:&#x20;

Alfred, an Office Director with Network Admin permission level, would like to create a User Segment that will include all users that are registered with the companies: CableInc, Acme, and Electrician's Friend.

However, he only wants to include users from these companies' Seattle locations in the USA.&#x20;

In order to fulfill these conditions, he sets up the following user segment:

<figure><img src="/files/kRK54aC2khIO0DWicmNk" alt="" width="563"><figcaption></figcaption></figure>

&#x20;He will utilize the condition field:

"Location = USA - Seattle"

and the condition fields:

"Organization = CableInc"

"Organization = Acme"

"Organization = Electrician's Friend"

The logic performs the **'AND'** operation between "Location = USA" and each value of "Organization = ..." The logic will also perform the '**OR**' operation between each value of "Organization =..." in the rule.&#x20;

So, essentially, the logic will search for users that meet the following criteria:

"Location = USA" **AND** "Organization = CableInc"

**OR**

"Location = USA" **AND** "Organization = Acme"

**OR**&#x20;

"Location = USA" **AND** "Organization = Electrician's  Friend"

***

### Configuring User Segment Settings

In the **Settings** tab, network admins can enter a label for the User Segment term your company would like to use. They can also manage who will be allowed to use user segments.&#x20;

<img src="/files/nRuuSoNeLR5r18HWQ0sM" alt="" width="563">

***

### SSO and Enterprise Apps Using User Segments

User Segments allow administrators to manage the visibility and accessibility of SSO and Enterprise Applications. By utilizing segments, you ensure that only authorized users can view or launch specific applications across the web and mobile platforms.

**Admin Configuration**

The **Audience** settings are managed within the **Add Application** or **Add Custom Application** dialogs for all MangoApps-provisioned SSO apps:

* **Everyone**: The default setting, making the application available to all users.
* **Specific User Segments**: Restricts the app to selected groups.
  * **Selection**: Admins can select up to 3 segments (Network, Guest, or Mixed).
  * **Visibility**: The SSO app list displays the current audience status for each app at a glance.
  * **Audit Logging**: All changes to an application's audience are recorded in the Audit Log under Domain Administration, including the user, time, and IP address.

**Security and Enforcement**

The platform enforces these permissions both in the user interface and at the server level:

* **Interface Filtering**: Users who do not belong to the authorized segments will not see the app in the My Enterprise Apps widget or the Top Navigation menu.
* **Mobile Sync**: These visibility rules are applied consistently across the mobile app and web experience.
* **Direct Access Protection**: If a user attempts to access an unauthorized app via a bookmark, direct link, or typed URL, they are blocked by a permission error screen: *"You don't have permission to access this application."*

{% hint style="warning" %}
If a configured segment is deleted, the app's audience must be updated. If no valid segments remain, the app is hidden from all users until a new segment is assigned.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.mangoapps.com/admin-guide/user-provisioning-and-management/user-segments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.