> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/install-and-configure-apps/oauth-2.0-setup/alternate-option-require-user-provided-credentials.md).

# Alternate option: require user-provided credentials

If you do not want to share your OAuth 2.0 connection, you can leave the credential fields blank. Leaving those fields blank requires end-users to enter their own OAuth 2.0 credentials in the Scenario editor.

You must then provide end-users with a redirect URI because your end-users need that redirect URI in order to create their own Client ID and Client secret. Make's public help center has information on how end-users can do this themselves.

{% hint style="warning" %}
Make's UI does not inform end-users that they must create and provide OAuth 2.0 credentials. Therefore, we recommend you inform your end-users and provide them with the necessary information.
{% endhint %}


---

# 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://developers.make.com/white-label-documentation/install-and-configure-apps/oauth-2.0-setup/alternate-option-require-user-provided-credentials.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.