# Productivity

The **Productivity Settings** configuration acts as the intelligence layer for We360.ai. Raw tracking data (e.g., active window titles or URLs) is meaningless without context. This section provides that context.

## Application & Domain Policies

The heart of the tracking engine is categorization.

* Define which applications and domains are universally considered **Productive**, **Neutral**, or **Unproductive** across the entire organization.
* **Role-Based Overrides**: We360.ai recognizes that "Productive" means different things to different teams. You can configure overrides so that *Facebook.com* is flagged as "Productive" for the Marketing team, but "Unproductive" for the Engineering department.

## Category Mapping

To streamline the overwhelming amount of software in use today, map individual applications into broader categories (e.g., *GitHub* and *VS Code* map to "Development Tools," while *Slack* and *Teams* map to "Communication"). These categories power the high-level dashboards in the Productivity Suite.

## Goal Setting

We360.ai shifts the focus from simply working *longer* to working *smarter*.

* Establish target productivity percentages (e.g., a goal of 70% productive time per shift).
* Establish activity score baselines that employees should strive to meet, gamifying the effort to remain engaged.

## How-to Guides

### Application Policies

<details>

<summary>Creating an Application Policy</summary>

An application policy defines which categories count as productive, unproductive, or neutral for a specific team context.

1. Navigate to **Settings > Productivity Rules**. The page shows existing policies on the left and category labels on the right. The **Application Policy** and **Mapping** tabs are at the top.
2. Click the **purple plus icon** to add a new policy.
3. Enter the **Application Policy Name** (mandatory) and click **Submit**.
4. Select the newly created policy. On the right, assign each category a label: **Productive**, **Unproductive**, or **Neutral**.

{% hint style="info" %}
Consider naming the policy after the team it will serve (e.g., "Design Team Policy") to simplify assignment later.
{% endhint %}

After creating the policy:

* Assign it to a team (see below).
* Map applications and URLs to categories so the labels take effect.

</details>

<details>

<summary>Editing an Application Policy</summary>

You can make two types of edits:

**Rename the policy:**

1. Click the pencil icon next to the policy name.
2. Change the name in the popup and click **Submit**.

**Reassign category labels:**

1. Select the policy.
2. For each category on the right, switch between the **Productive**, **Unproductive**, and **Neutral** labels as needed.

Changes save immediately.

</details>

<details>

<summary>Assigning a Policy to a Team</summary>

1. Navigate to **Settings > Teams**.
2. Select the target team.
3. Under the **Team Info** tab, open the **Application Policy** dropdown.
4. Select the desired policy. A confirmation message confirms the assignment.

</details>

### Category Mapping

<details>

<summary>Mapping Applications and URLs to Categories</summary>

1. Navigate to **Settings > Productivity Rules** and switch to the **Mapping** tab.
2. The tab lists all applications and URLs observed across your organization. Each entry has a category dropdown.
3. Select the appropriate category for each app or URL.
4. Use the **All / Mapped / Unmapped** filter buttons to focus on entries that still need categorization.

{% hint style="warning" %}
Regularly check the Mapping tab for newly detected applications and URLs. Unmapped entries will not count toward productivity calculations.
{% endhint %}

</details>

<details>

<summary>Can I Create Custom Categories?</summary>

No. Categories are predefined and cannot be created or edited. They serve as fixed groupings (e.g., Social Media, Streaming, Chat & Messaging) that organize applications and URLs by purpose.

</details>


---

# 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.we360.ai/reference/work-and-time-management/user-interfaces/portal/settings-center/productivity.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.