> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/organisation/introduction.md).

# Introduction

GuardWare’s **ORGANISATION** section brings together the core settings you manage after deployment. Use it to control administrator access, connect Microsoft 365, Google Workspace, and configure how the platform sends system emails.

These guides cover the main organisation-level tasks that affect access, integrations, and communication.

For the best setup experience, add your management console users first, connect your Microsoft 365 tenant and Google Workspace, and then configure SMTP if you want emails sent from your own domain.

## Recommended setup order

1. Set up [Management Console Users](/organisation/organisation-setup/management-console-users.md) so the right administrators can access GuardWare.
2. Integrate [Microsoft 365](/organisation/integrations/microsoft-365.md) to enable Microsoft 365 monitoring and data access.
3. Integrate [Google Workspace](/organisation/integrations/google-workspace.md) to enable Gmail and Google Drive monitoring.
4. [Configure SMTP](/organisation/organisation-setup/configure-smtp.md) to send emails from your own mail server and domain.


---

# 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.guardware.com/organisation/introduction.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.