> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/mcp/security-and-permissions/permissions-and-privacy.md).

# Permissions and privacy

How selected access and existing Supply'd permissions control the data an AI client can read.

## Read-only by design

Supply'd MCP grants the `supplyd:mcp:read` scope. It can retrieve authorised information, but it cannot:

* create, update, approve or delete records;
* run imports or exports;
* change company settings or user permissions;
* make payments or perform other administrative actions.

## Effective access

The connection receives only the overlap of:

* the business areas you select on the approval page;
* the permissions assigned to your Supply'd user; and
* any company, location, warehouse or store restrictions on your account.

If an administrator later removes one of your Supply'd permissions, the connection loses that access automatically.

## What is shared with the AI client

When you ask a question, the Supply'd information needed to answer it is returned to the connected AI client. Your organisation should review that client's data controls, retention settings and acceptable-use policy before enabling the connection.

Supply'd does not return passwords, access tokens or other authentication secrets as business data.

## Choose the minimum access you need

For example, a person who only needs product recipes and production history can select Products and Production without granting Sales, Billing or company settings.

To change the selected areas, [reconnect or revoke the connection](/mcp/manage-your-connection/change-or-revoke-access.md).


---

# 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://help.supplyd.co/mcp/security-and-permissions/permissions-and-privacy.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.