> For the complete documentation index, see [llms.txt](https://docs.mews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mews.com/connector-api/guidelines/unused-permissions.md).

# Unused permission policy

Mews removes a **Mews Connector API** permission if an integration has not used it for 12 months. This reduces the data an integration can expose if its credentials are leaked or stolen.

## Scope

This policy applies to all **Mews Connector API** permissions and all integrations.

## What counts as use

A permission counts as used when an integration makes a successful request that requires it. This includes requests to operations controlled by the permission and requests that load data through an extent controlled by it. For example:

* A successful request to [Get all customers](https://docs.mews.com/connector-api/operations/customers.md#get-all-customers) uses the `Customer` permission.
* A successful request to [Get all accounting items](https://docs.mews.com/connector-api/operations/accountingitems.md#get-all-accounting-items) with the `CreditCardTransactions` extent uses the `CreditCard` permission.

Requests to deprecated operations or extents also count while they still work. Failed requests — for example, those that return a validation error — do not count.

Mews counts use across all enterprises connected to the integration. If the integration uses a permission for one enterprise, it keeps that permission for all enterprises.

## When Mews removes a permission

Mews reviews permission use at regular intervals. A permission may be removed when both of these conditions are met:

* The integration has not used the permission in the last 12 months.
* The integration was created at least 12 months ago.

The age requirement gives each new integration at least 12 months to begin using its permissions.

## What happens when a permission is removed

The integration keeps its other permissions, and its access tokens remain valid. Mews does not send a separate notice; this policy page is the notice.

If the integration has not used any of its permissions for 12 months, Mews removes all of them. Until a permission is restored, the integration cannot read or change data.

A request that requires a removed permission returns `403 Forbidden`. The response message names the permission and refers to this policy. See [403 Forbidden](https://docs.mews.com/connector-api/guidelines/responses.md#403-forbidden).

## How to restore a permission

Contact the Partner Success team at <partnersuccess@mews.com> and provide:

* The integration's name.
* The permission you need.
* What the integration uses the permission for.

Partner Success reviews the request and restores the permission. This policy applies to restored permissions too: the 12-month period starts again on the date the permission is restored.

## Why Mews removes unused permissions

Each permission grants access to data. If an integration's credentials are leaked, an attacker could access the data allowed by its permissions. Removing permissions the integration does not use reduces that exposure.


---

# 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.mews.com/connector-api/guidelines/unused-permissions.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.
