> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/optimizing-productivity-and-focus/defining-productive-work.md).

# Defining "Productive" Work

The platform's productivity engine is only as accurate as its categorization rules. This guide walks you through setting up role-specific productivity definitions.

## Understanding Categorization

We360.ai classifies every application and website into one of three categories:

| Category         | Description                       | Example                |
| ---------------- | --------------------------------- | ---------------------- |
| **Productive**   | Work-relevant tools for this role | VS Code for developers |
| **Neutral**      | Uncategorized or ambiguous tools  | System utilities       |
| **Unproductive** | Non-work-related platforms        | Social media           |

## Configuration Steps

{% stepper %}
{% step %}

#### Set Organization-Wide Rules

Go to **Settings → Productivity**. Use the default rules panel to classify apps and URLs that apply universally (e.g., marking social media as "Unproductive" for everyone).
{% endstep %}

{% step %}

#### Add Role-Based Overrides

Use **Role-Based Overrides** to customize for specific teams. Example: mark `Facebook.com` as "Productive" for the Marketing team, but leave it "Unproductive" for Engineering.
{% endstep %}

{% step %}

#### Review Neutral Apps Regularly

Visit the **Analytics → Productivity** dashboard weekly to review apps that are still "Neutral". Categorize them to get a more accurate organizational productivity score.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Well-configured categorization rules are the most impactful configuration you can do. They directly determine the accuracy of each employee's productivity score.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/how-to-and-best-practices/optimizing-productivity-and-focus/defining-productive-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.