> 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/reference/user-interfaces/portal/universal-tools/integrations.md).

# Integrations

We360.ai is designed to act as the single source of truth for workforce analytics, but that data is most powerful when it flows seamlessly into your existing tech stack.

## Integration Dashboard

The **Integrations Dashboard** acts as the command center for monitoring the health and outputs of your connected applications (e.g., mapping data to Workday, syncing with Microsoft Teams, or piping timesheets to Jira).

<details>

<summary>Data Synchronization &#x26; Status</summary>

The primary feature of the dashboard is the **Status Distribution**, which calculates the synchronization health of your workforce.

* It visually categorizes users into specific statuses based on the integrated data (e.g., Red, Green, Overworked, OOO/Absent, Data Missing).
* Managers can toggle the underlying calculation (Active Time vs. Productive Time vs. Online Time) to shift the lens through which employee health is viewed.

</details>

<details>

<summary>Actionable Scenarios</summary>

Rather than just presenting a list of errors, the dashboard highlights specific **Actionable Scenarios** where integrations have run into logical roadblocks.

* **Intelligent Suggestions**: The system identifies discrepancies (e.g., "Employee is marked OOO in Workday but logged 4 hours in We360") and provides targeted suggestions on how to resolve the conflict.
* **Impacted Users**: Hovering over an alert immediately shows exactly which employee IDs are triggering the integration failure, allowing for rapid troubleshooting.

</details>


---

# 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/reference/user-interfaces/portal/universal-tools/integrations.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.