Worklabs' segmentation feature allows dynamic and static user grouping, enhancing filtering across topics and dashboards

Updated over a week ago

Worklabs ship with a feature to segment your end-users, allowing you to filter by these segments across topics, dashboards and stories. This enables a higher degree of filtering across them

Creating a segment

In Worklabs, account holders can create people segments via the admin console, choosing between dynamic and static types. Dynamic segments automatically update members based on source system profiles, whereas static segments require manual member selection by the administrator. Each segment must be named (mandatory) and can include an optional description. Additionally, segments can be nested within groups. Detailed interactions between groups and segments are explained in subsequent sections.

Types of Segments

In Worklabs, segments can be set as one of two types:

  1. Static

  2. Dynamic

Dynamic segments

In Worklabs, when setting up dynamic segments, you establish membership criteria based on current user profiles in the source system. This involves creating rules that consist of the property name which holds the value, a condition, and a value. Users who fulfil the conditions of these criteria are automatically included in the segment.

Below are the options available for profile fields and filters.

Property name

  • Position

  • Department

  • Division

  • Location

  • Organisation

  • Frontline

  • Direct Reports

  • Account Status

  • Tenure at Business (months)

  • Tenure at Business (years)

  • Tenure on Workplace (Months)

  • Tenure on Workplace (Years)


  • Starts with

  • Ends with

  • Contains

  • Equals

  • Does not start with

  • Does not end with

  • Does not contain

  • Does not equal


For these rules, the value can be any text, including letters, numbers, and symbols. You can set criteria using one rule, or combine several with and/or clauses. In cases with multiple rules, if a user matches any one of these rules, they are included in the segment.

Static segments

Static segments are easily configured by selecting an individual from the list of end-users provisioned in Worklabs. Additional setup options for static segments include specifying a start and end date. By determining these date ranges, you can establish when individuals should be included in, or removed from, a particular group. A practical application for using static segments could be for managing temporary employees or contractors, who may be limited both in number and in the duration of their stay with the business.

A more illustrative example of utilising static segments is the creation of a "Leadership" group. This approach can be more effective than relying solely on dynamic fields, as roles and positions may not comprehensively capture all individuals in leadership positions within the organisation.

Managing segments

As part of managing segments in Worklabs, you can archive or update a segment. Archiving a segment will remove it from the active segments view under the admin console. You can always go into the archived segments view to unarchive a segment.

Both Dynamic and Static groups include the following options once created

  • Manage end users

  • Edit segment

  • Archive segment

  • Assign to leadership page

Archive segment and Assign to leadership page have the same effect irrespective of the segment type. The Archive segment option will simply archive the group, as a result removing it from the active segments view and making it available only via the archived segments view.

Creating a group

Administrators in Worklabs can organise segments more effectively by creating groups. Within each group, they can nest various relevant segments. This grouping method ensures a comprehensive view, as it aggregates all members from the nested segments. For a clearer understanding, imagine a group named 'Project Teams.' This group might include segments like 'Design,' 'Development,' and 'Quality Assurance,' with 5, 10, and 4 members respectively. The 'Project Teams' group would then collectively display a total count of 19 members, representing the sum of individuals from all its nested segments.

Did this answer your question?