# Settings

### Monetization account status and Upgrade CTA

A default UI component shows what is the monetization status for the current user. It displays if the user is subscribed or not.&#x20;

If the user is not subscribed then there is a "unlock premium" CTA with a description you can customize.&#x20;

{% hint style="info" %}
Put in the description the unique features accessible only behind your paywall
{% endhint %}

If the user is subscribed the UI component displays the user is pro, what plan he selected and until when he's pro.

### Theme

The user is able to select the application theme. By default the theme is put on system but the user can choose light, dark or system.&#x20;

Learn more about theming [here](/features/theme.md).

### In-App rating

The settings screen displays a CTA to improve app rating. It calls the native in-app rating on both Android and iOS.

### Log out

By default the settings screen comes with a log out button that log out user from Firebase. By default AppKickstarter comes with an `observeSession` that changes the screen (replace all) after logout. But you can change this by changing the ~~observeSession~~ or doing a custom implementation on log out click.

Learn more about authentication, login and logout flows and observeSession [here](/features/authentication.md).

### App version

It displays the app version (version code + version number)

### User ids

It displays the firebase user id and the revenue cat user id.&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.appkickstarter.com/features/settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
