> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/features/main-integration/sharinpix-language-translation.md).

# SharinPix Language Translation

The components and features included in SharinPix package are in english by default.

However, changing the language from english to french provides translation for some SharinPix components/features such as the SharinPix Album component, the SharinPix Global Settings among others.

To change the language for SharinPix, proceed as follows:

* Open the SharinPix Admin Dashboard
* From the top menu bar, click on **Settings**
* Then click on the button **Edit Organization**
* Next, set your prefered language (**en** or **fr**) in the field labelled as **Locale**

![](https://2221230591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5EvYRrLbUyvRh8o1jmMG%2Fuploads%2FZXUkviQuyXQnsYwtFBF6%2Fimage%20\(17\).png?alt=media\&token=d7c84c72-4e3b-4e1d-902f-38c7840484ec)

{% hint style="info" %}
If you want to provide more translation for SharinPix, you can use the **Translation Workbench** provided by Salesforce.

Translation Workbench is a feature which once enabled, helps you translate almost everything in your organisation ranging from Salesforce standard objects, labels and customisations such as custom field labels, picklist values and Visualforce page contents.

You can also use **Rename Tabs and Labels** to rename SharinPix tabs and labels.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sharinpix.com/documentation/features/main-integration/sharinpix-language-translation.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.