> 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/documentation/partner-portal/partner-portal-detailed-guides/organisation.md).

# ORGANISATION

Organisations are customer environments managed under your partner account. Each organisation represents an individual customer and maintains its own users, products, databases, and licence configurations.

## Adding an Organisation

1. Navigate to **ORGANISATION** and click **+Add Organisation**.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2F5sSHzXsW1XMUutn3TWN7%2Fimage.png?alt=media&amp;token=a674341f-4299-45c3-ba76-8251592b0eea" alt="" width="563"><figcaption></figcaption></figure></div>

{% stepper %}
{% step %}

### Organisation Details

Enter the organisation's information.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2Fz7vWcH3NSg3dgjkLcFBy%2Fimage.png?alt=media&amp;token=6a03f722-21bc-48c4-a175-3f4c09bb5c6f" alt="" width="563"><figcaption></figcaption></figure>

1. **Organisation Name:** Enter the official name of the organisation.
2. **Timezone:** Select the organisation’s primary timezone from the dropdown.
3. **Country:** Choose the country where the organisation is based from the dropdown.
4. **City:** Enter the city of the organisation’s main office.
5. **Street Address:** Provide the full street address of the organisation.
6. **Website:** Enter the organisation’s official website URL (if available).
7. **Sector:** Select the industry or sector the organisation operates in.
8. **Organisation Logo:** Upload the organisation’s logo for display within the platform. Recommended size is **200 x 200 px** with a maximum file size of **2 MB**. Supported formats are `PNG`, `JPG`, `JPEG`, `SVG`, and `WEBP`.
   {% endstep %}

{% step %}

### Contact Details

Enter the organisation’s contact details. Designate at least one contact as the **primary contact**, who will act as the main point of contact between the organisation and the partner.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FJERCaE34b1RUxzvvd9xT%2Fimage.png?alt=media&amp;token=54a7d48b-c2a3-43c6-a5b1-f80e06ed31e9" alt="" width="563"><figcaption></figcaption></figure>

1. **Name:** Enter the contact person’s full name.
2. **Email:** Enter a valid email address for communication and account-related notifications.
3. **Phone Number:** Enter a contact number, including country code.
4. **Designation:** Enter the contact person’s job title or role.
5. **Department:** Specify the department the contact belongs to (e.g., Sales, IT, Support).
6. **Is Primary Contact Person:** Designates the primary contact for the organisation account. Only one primary contact can be set, and at least one is required.
7. **Is System Account:** Creates a portal account for the contact. Login credentials are sent automatically to the provided email address upon creation.
8. Click **+Add Contact** and click **Next**.
   {% endstep %}

{% step %}

### Select Products

Partners can assign products and issue licences to the organisations they manage.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FeJAZzGwaF5Ckp0leIE14%2Fimage.png?alt=media&amp;token=88b23353-12e5-4b9a-ab36-17c2ce373ba7" alt="" width="563"><figcaption></figcaption></figure>

1. Expand the product list to choose which products to make available to the organisation.
2. Select a licence to assign to the organisation. **Only one licence** can be assigned per product at a time. They are categorised as follows:

<table><thead><tr><th width="189">Licence Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Trial</strong></td><td>Provides temporary access for evaluation purposes. A user limit must be set at the time of assignment.</td></tr><tr><td><strong>Per User</strong></td><td>Charged per named user. A licence duration must be set at the time of assignment.</td></tr><tr><td><strong>Per GB</strong></td><td>Charged based on the volume of data processed. A licence duration must be set at the time of assignment.</td></tr><tr><td><strong>Campus Licence</strong></td><td>Covers all users within a defined site or campus under a single licence. A licence duration must be set at the time of assignment.</td></tr><tr><td><strong>NFR (Not for Resale)</strong></td><td>For internal use, testing, or demonstrations only. Cannot be used for commercial deployments. A duration and user limit must be set at the time of assignment.</td></tr></tbody></table>

3. After configuring the licences, click **Next**.
   {% endstep %}

{% step %}

### Templates

{% hint style="warning" %}
If you do not have any templates you can skip this section and configure them later after creating an organisation. Check the [**Templates**](/documentation/partner-portal/partner-portal-detailed-guides/templates.md) guide for more information.
{% endhint %}

Templates allow partners to define and roll out consistent data types and PROTECT configurations across multiple organisations without having to configure each one individually.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FSEnEc4bkX03kYeFVCg1g%2Fimage.png?alt=media&amp;token=54202173-20ec-46a1-9425-4d321ff2a154" alt="" width="563"><figcaption></figcaption></figure>

1. From the list:
   1. **Assign a Data Type Template**
      1. Select a **Data Type Template** from the dropdown.
   2. **Assign an INSIGHT Template**
      1. Select an **Advanced Setting** from the dropdown.
      2. Select a **User Policy** from the dropdown.
      3. Select a **Working Days Template** from the dropdown.
   3. **Assign a PROTECT Template**
      1. Select a **User Policy** from the dropdown.
      2. Select an **Application Template** from the dropdown.
      3. Select an **Avoid Folder Template** from the dropdown.
2. Click **Next**.
   {% endstep %}

{% step %}

### Review & Activate

Review the entered details and activate the organisation.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FPyYoVY73SPkfS33njPWb%2Fimage.png?alt=media&amp;token=07e62292-5fa3-4f25-87b5-ab1b69a8b9f6" alt=""><figcaption></figcaption></figure>

1. After reviewing, click **Submit**.
2. If you wish to make changes, click **Back** to go back and edit the desired details.
3. Once activated, the organisation's environment is provisioned and ready for access.
   {% endstep %}
   {% endstepper %}

## Organisation Management

Once an organisation has been created, its details, users, and assigned products can be managed as needed. The available management functions are provided through the **Actions** menu in the **ORGANISATION** section.

### Manage Organisation

Update an organisation's details, contact information, and assigned products as needed. You can review and modify the organisation's configuration to keep its information and product assignments up to date.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FABBtPqcWuCALzheNGA5g%2Fimage.png?alt=media&amp;token=08b87798-658c-486d-a7d4-ba9c7304e72c" alt="" width="563"><figcaption></figcaption></figure>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Organisation**.
3. Click **Edit** <i class="fa-pencil">:pencil:</i> on the section you want to update.
4. After making changes, click **Update** to save.

### Manage Users

Add and manage the users who will access a specific organisation's Management Console. Each user is scoped to their organisation only and has no visibility into the partner layer or other organisations.<br>

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2Fkq43GOCn7EK6zZjUy0Fd%2Fimage.png?alt=media&amp;token=1b87da83-0d29-40e6-bf0b-13ed8fdb7f87" alt="" width="563"><figcaption></figcaption></figure>

<details>

<summary><strong>Add Organisation User</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Users**.
3. Click **+Add User**.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FMS5WMOBCFfwqwU4FibIO%2Fimage.png?alt=media&amp;token=19526c49-89d9-4a08-a8f3-628ea8abc44c" alt="" width="563"><figcaption></figcaption></figure></div>
4. Enter the user's name, email, and contact number.
5. Click **Create**.

</details>

<details>

<summary><strong>Edit Organisation User</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Users**.
3. Click **Edit** <i class="fa-pencil">:pencil:</i> to open the window and make changes.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FZO1kawkVrAoOFfpyXfur%2Fimage.png?alt=media&amp;token=4b75d737-de84-4782-bb3d-8860ebac6f4b" alt="" width="352"><figcaption></figcaption></figure></div>
4. Click **Update** to save.

</details>

<details>

<summary><strong>Disable Organisation User</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Users**.
3. Click **Disable** <i class="fa-trash-can">:trash-can:</i> to suspend the user's account.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FyNQcATa1zUw8Md2o87ju%2Fimage.png?alt=media&amp;token=179e15cd-9b49-4459-bfb2-306d35e4eabc" alt="" width="352"><figcaption></figcaption></figure></div>
4. Click **Disable** again to confirm.

</details>

<details>

<summary><strong>Restore Organisation User</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Users**.
3. Click **Restore** <i class="fa-rotate-left">:rotate-left:</i> to reactivate a disabled account.

</details>

<details>

<summary><strong>Send Invitation</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Users**.
3. Click **Send Invitation** <i class="fa-envelope">:envelope:</i> to resend a login invite.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FOTkPqebd7laRjqgpEibg%2Fimage.png?alt=media&amp;token=ef95e08d-d90c-41d8-ac69-ec15465d4c03" alt="" width="352"><figcaption></figcaption></figure></div>
4. Click **Send Invitation** to confirm action.

</details>

<details>

<summary><strong>Reset Password</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Users**.
3. Click **Reset Password** <i class="fa-key">:key:</i> to open the password configuration window.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FqIu527V1uFGKZ0qKYMmM%2Fimage.png?alt=media&amp;token=3d831f91-bbad-4bf9-b3ad-bcc64b5dbca5" alt="" width="352"><figcaption></figcaption></figure></div>
4. Enter the new password and click **Reset**. Changes to user access take effect immediately.

</details>

### Manage Products

Assign GuardWare products to an organisation and allocate the appropriate licences for each. Licences control how many users or devices within an organisation can access an assigned product and are tracked at the partner level.

<figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FKYTM85IjgmWJH6zODVGy%2Fimage.png?alt=media&amp;token=0155a335-d895-4bcb-8d7a-b859b4053f20" alt="" width="563"><figcaption></figcaption></figure>

<details>

<summary><strong>Assign New Product</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Products**.
3. Click **+Assign New Product** to assign a product to the organisation.
4. Select a product from the dropdown and choose the licence type.

<table><thead><tr><th width="189">Licence Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Trial</strong></td><td>Provides temporary access for evaluation purposes. A duration and user limit must be set at the time of assignment.</td></tr><tr><td><strong>Per User</strong></td><td>Charged per named user. A licence duration must be set at the time of assignment.</td></tr><tr><td><strong>NFR (Not for Resale)</strong></td><td>For internal use, testing, or demonstrations only. Cannot be used for commercial deployments. A duration and user limit must be set at the time of assignment.</td></tr><tr><td><strong>Per GB</strong></td><td>Charged based on the volume of data processed. A licence duration must be set at the time of assignment.</td></tr><tr><td><strong>Campus</strong></td><td>Covers all users within a defined site or campus under a single licence. A licence duration must be set at the time of assignment.</td></tr></tbody></table>

5. Set the licence duration and licence count for the organisation if required.
6. Click **Save** to apply the changes.

{% hint style="info" %}
By default, licences are in a **Not Activated** state. The status changes to **Active** automatically once an agent connection is established.
{% endhint %}

</details>

<details>

<summary><strong>Update Products</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Products**.
3. Click **Actions** on the desired product and click **Update** <i class="fa-pencil">:pencil:</i>.
4. Click **Save** after making changes. Applies to licences that are **'not activated'** only.

</details>

<details>

<summary><strong>Delete Products</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Products**.
3. Click **Actions** on the desired product and click **Delete** <i class="fa-trash-can">:trash-can:</i>.
4. Click **Delete** again to confirm. Applies to licences that are **'not activated'** only.

</details>

<details>

<summary><strong>Renew Products</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Products**.
3. Click **Actions** on the desired product and click **Renew** <i class="fa-arrow-rotate-right">:arrow-rotate-right:</i>.
4. Click **Renew** again to confirm. Applies to licences that are **'active'** only.

</details>

<details>

<summary><strong>Deactivate Products</strong></summary>

1. Navigate to **ORGANISATION**.
2. Click **Actions** on the desired entry and select **Manage Products**.
3. Click **Actions** on the desired product and click **Deactivate** <i class="fa-circle-x">:circle-x:</i>.
4. Click **Deactivate** again to confirm. Applies to licences that are **'active'** only.

{% hint style="warning" %}
Deactivating a product stops the organisation's active access to that product. Use this only when you intend to end service for that organisation.
{% endhint %}

</details>

### Deactivate/Reactivate Organisation

Temporarily deactivate an organisation when it is no longer required to remain active in the Partner Portal. While deactivated, the organisation's users and assigned products are inaccessible, and another organisation with the same name cannot be created.

#### Deactivate an Organisation

1. Navigate to **ORGANISATION**.
2. On the desired organisation entry, click **Actions** and click **Deactivate**.

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FM9FQkQ0Bb3GryX5Rwlvs%2Fimage.png?alt=media&amp;token=78405910-fce2-497e-b5fc-855072327426" alt="" width="473"><figcaption></figcaption></figure></div>
3. On the pop up window, click **Deactivate** again which opens up a confirmation field.&#x20;
4. Type 'Confirm' in the field and click **Delete**. &#x20;

#### Reactivate Organisation

A **Partner Admin** can re-enable the organisation after which its users and products are automatically enabled again.&#x20;

1. Navigate to **ORGANISATION**.
2. Click <i class="fa-bars-filter">:bars-filter:</i> **Filter**, select **Filter By Status**, click the dropdown, select **Deactivated** and click **Apply**.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FD1drxwfONMUU4hrki6z0%2Fimage.png?alt=media&amp;token=1437bdec-14f7-44fa-9c38-7353f0a3d308" alt="" width="563"><figcaption></figcaption></figure></div>
3. On the desired organisation click **Actions** and select **Restore Organisation**.

### Manage Cloud Monitoring

{% hint style="warning" %}
Ensure [**Microsoft 365**](/documentation/management-console/integrations/microsoft-365.md) is integrated before proceeding with this step.
{% endhint %}

Configure and manage cloud monitoring for the organisation's Microsoft 365 and Google Workspace environments. This controls the cloud activity monitoring settings used to capture and analyse relevant user and file activities.&#x20;

1. Navigate to **ORGANISATION**.
2. On the desired organisation click **Actions** and click **Manage Cloud Monitor**.<br>

   <div align="left"><figure><img src="https://1250802615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBhuCCosRTuEk4psD8h4o%2Fuploads%2FBCQRK3EirdepcNIpjM3g%2Fimage.png?alt=media&amp;token=6e03e146-b5cc-4c1e-980b-e9d4029d3ce0" alt="" width="563"><figcaption></figcaption></figure></div>
3. Toggle Monitoring **On** or **Off** for each service and click **Save** to apply changes.

### Access the Organisation's Management Console&#x20;

Once an organisation is set up, partners can switch into that organisation's Management Console at any time, given the proper access. This gives direct access to organisation-level setup, validation, and troubleshooting without requiring separate login credentials.

{% hint style="info" %}
Use organisation access when you need to verify product setup, review the customer environment, or complete tasks that only exist inside the organisation's Management Console.
{% endhint %}

1. To switch to an organisation, click the **Partner** button at the top of the screen.
2. From the dropdown, click the organisation you want to navigate to.
3. To return to the Partner Portal, click the **Partner** button at the top of the screen again.
4. Select **Return to Partner** from the dropdown.

## Additional Configurations

### Microsoft 365

{% hint style="info" %}
An active Microsoft 365 account with **Global Administrator** credentials is required to connect Microsoft 365 services to an organisation.
{% endhint %}

Connecting Microsoft 365 grants GuardWare the permissions required to scan and manage content across Exchange Online and SharePoint. This integration also allows syncing of classification labels from Microsoft Information Protection; therefore, this operation must be completed before GuardWare can operate within the organisation's Microsoft 365 environment.

1. Navigate to **ORGANISATION** > **M365 Integration**.
2. Click **Connect M365**.
3. Select or add the Global Administrator account. GuardWare requests the following permissions automatically during the Microsoft 365 consent flow:

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="219">Permission</th><th>What It Allows</th></tr></thead><tbody><tr><td><strong>Files.Read.All</strong></td><td>Read all files across SharePoint and OneDrive</td></tr><tr><td><strong>Files.ReadWrite.All</strong></td><td>Read and write all files across SharePoint for remediation</td></tr><tr><td><strong>Group.Read.All</strong></td><td>Read Microsoft 365 group metadata</td></tr><tr><td><strong>GroupMember.Read.All</strong></td><td>Read group membership lists</td></tr><tr><td><strong>Mail.Read</strong></td><td>Read all mailbox content</td></tr><tr><td><strong>Mail.ReadBasic.All</strong></td><td>Read mail headers and metadata</td></tr><tr><td><strong>Mail.ReadWrite</strong></td><td>Required to delete, move, or mark emails in Exchange Online</td></tr><tr><td><strong>MailboxSettings.Read</strong></td><td>Access mailbox rules, auto-replies, and related settings</td></tr><tr><td><strong>Sites.FullControl.All</strong></td><td>Full access, including management actions</td></tr><tr><td><strong>Sites.Read.All</strong></td><td>Read SharePoint site metadata and structure</td></tr><tr><td><strong>User.Read.All</strong></td><td>Read all user profiles including name, email, role, and department</td></tr></tbody></table>

4. Select **Consent on behalf of your organisation** and click **Accept**. A confirmation screen will be displayed upon successful connection to Microsoft 365 services.

### SMTP&#x20;

SMTP configuration is an organisation-level setting. When configured, system-generated emails, user invitations, alert reports, and account activation emails are sent to organisation users from the configured SMTP server. If left unconfigured, email notifications will be sent via the default server shipped with the product.

{% hint style="info" %}
Configure SMTP on behalf of each organisation if:

* The organisation requires all system emails to come from their domain for security or compliance reasons.
* The organisation's email security policies block emails from external or unrecognised domains.
* The organisation requires brand consistency across all communications sent to its users.
  {% endhint %}

1. Navigate to **Organisation** > **SMTP Configuration**.
2. In the **SMTP Server** field, enter the mail server address (e.g., *smtp.office365.com*).
3. In the **SMTP Port** field, enter the port number the server uses. Common values are:

<table><thead><tr><th width="85.12908935546875">Port</th><th width="182">Protocol</th><th>Use</th></tr></thead><tbody><tr><td>25</td><td>SMTP</td><td>Default mail transfer. Often blocked by ISPs for outbound mail.</td></tr><tr><td>465</td><td>SMTPS</td><td>SMTP over SSL. Used for encrypted connections.</td></tr><tr><td>587</td><td>SMTP + STARTTLS</td><td>Recommended for most modern email servers.</td></tr></tbody></table>

4. In the **SMTP Username** field, enter the username of the email account that will send notifications.
5. In the **Email** field, enter the email address that will appear in the From field of notifications (e.g., *<noreply@yourcompany.com>*).
6. In the **Password** field, enter the password for the SMTP account.
7. In **Enable STARTTLS**, select **Yes** if your email server requires STARTTLS encryption. STARTTLS encrypts the connection between the management console and your email server, protecting credentials and message content. Most modern email servers require this. Otherwise, select **No**.
8. In **Enable SMTP Authentication:**
   1. Select **Yes** if your server requires a username and password before sending emails.
   2. Select **No** if your server allows sending without authentication.
9. In the **Test Email Address** field, enter an email address to receive a test message and verify the configuration.
10. Click **Save** to apply changes.


---

# 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/documentation/partner-portal/partner-portal-detailed-guides/organisation.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.
