> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/phishing/tenant-statuses.md).

# Tenant statuses

Each connected tenant has a status that tells you whether campaigns can run. Find it in `Overview` > `Settings`.

<table><thead><tr><th width="131.25390625">Old Status</th><th width="144.00390625">New Status</th><th>Meaning</th><th>Impact on campaigns</th></tr></thead><tbody><tr><td><strong>Active</strong></td><td><strong>Active</strong></td><td>All systems operational</td><td>Phishing fully operational</td></tr><tr><td><strong>Setup pending</strong></td><td><strong>Pending</strong></td><td>Email delivery configuration in progress</td><td>Campaigns cannot be sent yet</td></tr><tr><td><strong>Setup failed</strong><br><strong>Not set up</strong></td><td><strong>Delivery error</strong></td><td>Email delivery is not configured or has failed</td><td>Campaigns cannot be sent</td></tr><tr><td></td><td><strong>Restricted</strong></td><td>Additional permissions required for group sync</td><td>Employee groups are not synced</td></tr><tr><td><strong>Unsynced</strong></td><td><strong>Disconnected</strong></td><td>Directory connection lost</td><td>Employees not synced, campaigns paused</td></tr></tbody></table>

## Active

Everything is working as expected. Employees are synchronized from your directory, groups are available for targeting, and phishing emails can be delivered directly to inboxes. No action is required.

## Pending

Email delivery is being configured. This usually takes a few seconds after completing the email deliverability setup. If the status does not change after 15 minutes, refresh the page or contact Stoïk support.

## Delivery error

Email delivery is either not configured or the configuration has failed. Phishing emails cannot be delivered to employee mailboxes and campaigns do not work.

Possible causes:

* Email deliverability was never configured after connecting the tenant
* A previous configuration attempt failed
* Permissions were revoked on the email provider side

To fix it:

1. Go to `Overview` > `Settings`.
2. On the affected tenant, click `...` > `Restart the configuration`.
3. Follow the email deliverability [setup](/human-security/phishing/setup.md) instructions.

## Restricted

Your tenant is connected and employees are synchronized, but Stoïk Protect is missing a permission to sync employee groups from Google Workspace or Microsoft 365. Campaigns still work for individual employees, but you cannot target groups.

To fix it:

1. Go to `Overview` > `Settings`.
2. On the affected tenant, click `...` > `Restart the configuration`.
3. Sign in with an administrator account and accept the new permission.

Groups sync automatically within a few minutes.

## Disconnected

The connection to your directory provider has been lost. Stoïk Protect can no longer synchronize employees or groups, and campaigns are paused.

{% hint style="warning" %}
This is the most critical status. No data is synced and no campaign can run until the connection is restored.
{% endhint %}

Possible causes:

* The administrator who authorized the connection has been removed from the organization
* Permissions were revoked from the Google or Microsoft admin console
* The tenant was deleted or reconfigured on the provider side

To fix it:

1. Go to `Overview` > `Settings`.
2. On the affected tenant, click `...` > `Restart the configuration`.
3. Sign in with an account that has administrator rights on the mailbox provider and grant all requested permissions, as described in [Setup](/human-security/phishing/setup.md).

Once reconnected, employees and groups sync again and campaigns resume automatically.

If a status does not resolve, contact Stoïk support at <protect@stoik.io>.


---

# 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.stoik.io/human-security/phishing/tenant-statuses.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.