> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/help-center/help-topics/connecting/regional-and-account-restrictions/oura-no-extra-setup-for-production.md).

# Does Oura need extra setup before production?

Oura requires no additional setup on your side before going to production.

**Oura requires no additional setup on your side** before going to production. Unlike WHOOP, you don't need your own Oura credentials. Using your own Oura app is optional. Use it as you would any other standard integration.

## Can Oura's consent screen show my app's name?

**Yes, with your own Oura developer app.** The consent screen is Oura's own, and it names the Oura app the connection runs through. By default that is Terra's, so users see Terra.

{% stepper %}
{% step %}
Create an app in [Oura's developer portal](https://cloud.ouraring.com/oauth/applications) and note its Client ID and Client Secret.
{% endstep %}

{% step %}
Register the redirect URI `https://access.tryterra.co/api/v3/auth/oura/oauth2`.
{% endstep %}

{% step %}
Contact Terra support to point your Oura connection at your app's credentials, for each environment you use.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Users who connected before the switch stay on the app they authorised, Terra's, until they reconnect.
{% endhint %}

Your own Oura app also means Oura's per-application rate limit counts only your users' requests.