> 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/readme.md).

# How To

We360.ai how-to guides for employee monitoring, productivity tracking, attendance management, and workforce analytics for HR and team leads.

The "Action" section with practical guides to help you get the most out of <code class="expression">space.vars.company\_name</code> features.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-clock">:clock:</i></td><td><strong>Mastering Time &#x26; Attendance</strong></td><td>Automate workday management, handle leave requests, and manage shift rotations.</td><td><a href="https://docs.we360.ai/how-to-and-best-practices/mastering-time-and-attendance.md">Mastering Time &amp; Attendance</a></td></tr><tr><td><i class="fa-chart-line">:chart-line:</i></td><td><strong>Optimizing Productivity &#x26; Focus</strong></td><td>Define productive work, set goals, and curb distractions effectively.</td><td><a href="https://docs.we360.ai/how-to-and-best-practices/optimizing-productivity-and-focus.md">Optimizing Productivity &amp; Focus</a></td></tr><tr><td><i class="fa-eye">:eye:</i></td><td><strong>Visibility, Accountability &#x26; Evidence</strong></td><td>Configure ethical monitoring and gain real-time insights into your team.</td><td><a href="https://docs.we360.ai/how-to-and-best-practices/visibility-accountability-and-evidence.md">Visibility &amp; Accountability</a></td></tr><tr><td><i class="fa-heart">:heart:</i></td><td><strong>Improving Employee Wellness</strong></td><td>Spot burnout early and drive engagement with data-driven insights.</td><td><a href="https://docs.we360.ai/how-to-and-best-practices/improving-employee-wellness.md">Improving Employee Wellness</a></td></tr><tr><td><i class="fa-chart-bar">:chart-bar:</i></td><td><strong>Data Intelligence &#x26; Reporting</strong></td><td>Automate reports and build custom KPIs for business intelligence.</td><td><a href="https://docs.we360.ai/how-to-and-best-practices/data-intelligence-and-reporting.md">Data Intelligence &amp; Reporting</a></td></tr><tr><td><i class="fa-person-circle-exclamation">:person-circle-exclamation:</i></td><td><strong>Support</strong></td><td></td><td></td></tr><tr><td><i class="fa-diagram-project">:diagram-project:</i></td><td><strong>Project Management</strong></td><td>Complete Features &#x26; User Guide</td><td></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/how-to-and-best-practices/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
