> 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/quick-start/essential-pre-flight-check.md).

# Essential Pre-Flight Check

Pre-deployment checklist for We360.ai — system requirements, firewall rules, and agent connectivity for employee monitoring setup.

Before deploying the agent across your organization, complete these checks to ensure a smooth rollout.

## System Requirements

| Requirement           | Minimum Spec                                    |
| --------------------- | ----------------------------------------------- |
| **Operating Systems** | Windows 10+, macOS 13+, Ubuntu 20.04+           |
| **RAM**               | 4 GB                                            |
| **Disk Space**        | 500 MB free (for agent + local data cache)      |
| **Network**           | HTTPS (TCP 443) outbound access to `*.we360.ai` |

## Connectivity Checklist

{% stepper %}
{% step %}

#### Verify Firewall Rules

Ensure that the target machine can reach We360.ai endpoints. All traffic uses **HTTPS/WSS on TCP port 443**.

Recommended wildcard rules:

* `*.we360.ai`
* `*.in.we360.ai` *(India region)*

Refer to the [Allowlist Guide](https://docs.we360.ai/deployment-and-it-ops/network-and-security-hardening/allowlist-guide) for the full URL list if wildcards are not supported.
{% endstep %}

{% step %}

#### Grant macOS Permissions

If deploying on macOS, ensure the following permissions are granted via **System Settings → Privacy & Security**:

* **Screen Recording** — required for screenshot capture.
* **Input Monitoring** — required for idle detection.
* **Accessibility** — required for reading application window titles.

{% hint style="warning" %}
Without these permissions, the agent will report zero productivity on macOS.
{% endhint %}
{% endstep %}

{% step %}

#### Disable AV/EDR Conflicts

If your organization uses antivirus or endpoint detection software (e.g., CrowdStrike, Defender, SentinelOne), add We360.ai process exclusions before installation. See the [AV & EDR Exclusions](https://docs.we360.ai/deployment-and-it-ops/network-and-security-hardening/av-and-edr-exclusions) guide.
{% endstep %}

{% step %}

#### Test the Agent

Install the agent on a single pilot machine first. Log in, let it run for 5–10 minutes, then verify that activity appears on the dashboard. Only then proceed with mass deployment.
{% endstep %}
{% endstepper %}


---

# 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/quick-start/essential-pre-flight-check.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.