> 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/faqs/sharinpix-not-working-on-salesforce-community.md).

# SharinPix not working on Salesforce Community

If you are encountering issues while using SharinPix on a Salesforce Community, here are some configurations that need to be looked into:

* **Check if SharinPix has been properly configured for Salesforce Community**\
  \
  The first thing that needs to be verified is whether SharinPix has been properly configure. Refer to the following article to cross-check the steps required for the configuration:\
  [Enable the usage of SharinPix in Salesforce Community](/documentation/features/main-integration/using-sharinpix-in-salesforce-community.md#enable-the-usage-of-sharinpix-in-salesforce-community)
* **Check if Community users have proper access rights to SharinPix**\
  \
  Some Community users do not have all access rights to SharinPix by default. To provide proper access rights to Community users using the SharinPix components, objects or features, refer to the following article:\
  [SharinPix Community users access rights](/documentation/access-and-security/sharinpix-community-users-access-rights.md)


---

# 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/faqs/sharinpix-not-working-on-salesforce-community.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.