> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/social-registry/features/languages-support/user-guides/set-language-preference.md).

# Set Language Preference

Social Registry

Social Registry (SR) has the option to load the application in multiple languages. Each user logging into the application can set the languages according to his/her preferences. This document provides instructions for the user to set their preferred language in the application. Once the preferred language is updated, the default language is changed to the preferred language in the user interface.

## Prerequisites

The user must have valid credentials to login to Social Registry.

## Procedure

1. Login to ***Social Registry***. Social Registry application is displayed.
2. Click the user profile at the top right corner of the application.

<figure><img src="https://1895884874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnKdOHLbjDdIln1QDNwSx%2Fuploads%2Fgit-blob-a04aa52a0f83220909de6748b498e590c3342b27%2Fuser-profile-sr.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Choose ***Preferences***.

***Change My Preferences*** screen is displayed.

4. Click the ***Preferences*** tab.
5. Select the preferred language in the ***Language*** drop-down.

<figure><img src="https://1895884874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnKdOHLbjDdIln1QDNwSx%2Fuploads%2Fgit-blob-aa69fb844ec4a7e38110c33443f07eec60b4fa52%2Flanguage-drop-down-sr.png?alt=media" alt=""><figcaption></figcaption></figure>

6. Click the ***Save*** button.

Once the preferred language is updated, the default language is changed to the preferred language in the user interface. For example,

<figure><img src="https://1895884874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnKdOHLbjDdIln1QDNwSx%2Fuploads%2Fgit-blob-db79b228e0b6e825badcdc2d4d4d44659549d0c1%2Fexample1-for-language-change-in-ui.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1895884874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnKdOHLbjDdIln1QDNwSx%2Fuploads%2Fgit-blob-7859fb6a5896eea5ada586404d884b968254bd66%2Fexample-for-language-change-in-ui.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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://docs.openg2p.org/1.3/social-registry/features/languages-support/user-guides/set-language-preference.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.