# Segments

The **Segments** feature in the[ Operator Backoffice ](/operator-backoffice/operator-backoffice-overview.md)(BO) enables operators to **save** and **reuse** filtered **views** **across** **different** **reporting** pages such as *Flagged Activity*, *Reports*, and more. Segments are designed to **speed up** day-to-day **monitoring**, **troubleshooting**, and **operational** **checks** by allowing users to create personalised views that can be shared and accessed easily.

<figure><img src="/files/w8CHrABQysm5l8Q21pq9" alt=""><figcaption></figcaption></figure>

#### Key Use Cases for Segments

* Save commonly used filtered views for regular monitoring.
* Share operational views with other team members securely.
* Bookmark frequently used filters to the sidebar for faster access.
* Maintain page-specific customisations across modules like Flagged Activity or Reports.

***

### Viewing and Managing Segments

#### Table View

In each module that supports Segments (e.g., Flagged Activity), a **'View all segments'** option is available. This opens a full list of all saved Segments for that specific page, including:

* **Segment name**
* **Notes** (optional)
* **Actions**: share, delete, bookmark/remove bookmark

Segments saved on other modules are not visible outside their respective pages. For example, a Segment saved under *Reports* will not appear under *Flagged Activity*.

#### Sidebar Segments

For faster access, Segments can be bookmarked to the left-hand sidebar. Only pinned Segments will appear in the sidebar. This is useful for views you access frequently.

***

### Creating a Segment

To save a filtered view as a Segment:

1. Apply your desired filters on the current page.
2. Click **‘Save Segment’**.
3. Enter a **name** (required) and an optional note. Notes are great for later, when you need to differentiate between a list of  Segments.&#x20;
4. Tick **‘Add to sidebar’** if you’d like to bookmark it.
5. Click **Save**.

The Segment is now saved and will appear under "*View All Segments"*.

{% hint style="info" %}
Your saved segments are device-specific, meaning they’ll only be available on the device where you created them.
{% endhint %}

<div><figure><img src="/files/fJgodXODAlpy9THmWDBx" alt=""><figcaption></figcaption></figure> <figure><img src="/files/w8CHrABQysm5l8Q21pq9" alt=""><figcaption></figcaption></figure></div>

***

### Sharing Segments

To share a saved filter view with someone:

1. Apply the filters you want to share.
2. Click **‘Share Segment’**.
3. A secure encrypted URL is copied to your clipboard.
4. Paste and send it via email or chat.

When the recipient opens the link:

* The filters will be auto-applied.
* If they do not have the necessary permissions, an error message will be shown.

<figure><img src="/files/LCemreJzXkXtyOdCW4Qq" alt=""><figcaption></figcaption></figure>

***

### Segment Behaviour and Security

* **Page-Specific:** Segments are stored per page. You cannot use a Segment saved on *Reports* in *Flagged Activity*.
* **Filters in URL:** Filters are encoded into the URL as they’re applied, ensuring persistence across refreshes and shared links.
* **Permissions:** Segments respect the underlying page access permissions of the user.
* **Device-Specific:** Segments are connected to the device you created them in and won’t sync across other devices.

***

### Frequently Asked Questions (FAQ)

**Can I use the same Segment across different pages?**\
No. Segments are page-specific and are only visible on the page where they were created.

**What filters are included in a shared Segment?**\
All filters visible in the UI for the page at the time of saving or sharing will be applied in the shared view.

**Is data in shared Segment links secure?**\
Yes. The URL is encrypted and does not expose any sensitive information such as usernames or internal IDs.

***


---

# 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://docs.hub88.io/operator-backoffice/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.