> 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/best-practices/view-upload-images-on-salesforce-classic-for-desktop.md).

# View / Upload images on Salesforce Classic for Desktop

SharinPix can be integrated into Salesforce Classic in different ways.

For instance, it is possible to integrate SharinPix into your own Visualforce development or add the same to your page layouts.

<figure><img src="https://1575680348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFH9adA1hWSw6Dv1DcZD%2Fuploads%2Fk5YQ0WN865E36G3gAODy%2Fimage.png?alt=media&amp;token=151a7c5c-979a-48df-8ef5-25130d7d130c" alt=""><figcaption></figcaption></figure>

Here are the possibilities you have :

* [Using SharinPix "Album" Canvas App](/getting-started/basic-setup/basic-setup-step-3a-for-classic-users-setup-sharinpix-for-salesforce-classic.md)
* [Using Visualforce page Without A Controller (Admin Friendly)](/documentation/features/main-integration/using-on-classic-with-a-visualforce-page-without-an-apex-controller-admin-friendly-version.md)
* [Using Visualforce page With a Controller (Developer skills required)](/documentation/features/main-integration/using-on-classic-with-a-visualforce-page-with-an-apex-controller-developer-skills-required.md)

The above links point to detailed instructions on how to configure each experience.

**Best Practice is to use the Visualforce page integration.**

If you want more flexibility, you should use the version with a Controller, but this requires some developer skills.


---

# 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/best-practices/view-upload-images-on-salesforce-classic-for-desktop.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.