> 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/how-sign-in-works.md).

# How sign-in works

What to expect when an AI client asks you to authorise Supply'd.

When you connect an AI client:

1. The client reads Supply'd's published OAuth settings.
2. Your browser opens the secure Supply'd sign-in and approval page at `app.supplyd.co`.
3. You sign in to Supply'd and choose the business areas to allow.
4. Supply'd returns you to the AI client.
5. The client receives a revocable, read-only access token; not your Supply'd password.

Your Supply'd password is entered only on the Supply'd website and is not shared with the AI client.

## Recognising the correct connection

| Purpose                        | Expected address                                              |
| ------------------------------ | ------------------------------------------------------------- |
| MCP server                     | `https://mcp.supplyd.co/`                                     |
| Supply'd sign-in and approval  | `https://app.supplyd.co`                                      |
| Protected-resource information | `https://mcp.supplyd.co/.well-known/oauth-protected-resource` |

If the sign-in or approval page appears on another domain, stop and do not approve it.

## Sessions and expiry

For security, an approval request can expire if it remains open too long or is reused. If Supply'd says the authorisation request is invalid or expired, close that window and start the connection again from your AI client.

Access tokens can also expire or be revoked. A compatible client will normally refresh access or ask you to reconnect.


---

# 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/how-sign-in-works.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.