> 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/user-receiving-error-message-you-do-not-have-access-to-the-apex-class-named-sharinpixlightningcontro.md).

# User receiving error message 'You do not have access to the Apex class named 'SharinPixLightningController' when trying to access a SharinPix component. What should I do?

![](https://751044238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi8tH1o5AHthxksYgF6ij%2Fuploads%2FjoENscE2in30o9hdQiQm%2Fimage%20-%202026-01-28T164723.513.png?alt=media\&token=2a7ac5f0-5491-49f8-8bc7-13b56088f72d)

Error messages such as '**You do not have access to the Apex class named 'SharinPixLightningController'** ' (or another class name: '*You do not have access to Apex class name \[ApexClassName]* ') mostly occur when a non-admin user try to access a SharinPix component.

This is due to the following Salesforce critical update: **Restrict Access to @AuraEnabled Apex Methods for Authenticated Users Based on User Profile**

To resolve this, simply assign the permission set named **SharinPix Lightning Components** to the user encountering this error message. The SharinPix Lightning Component permission set gives access to SharinPix's Apex classes.

{% hint style="success" %}
This will be automatically activated in August 2020 unless otherwise stated by Salesforce.
{% endhint %}

{% hint style="warning" %}
**Note:**

If the permission set **SharinPix Lightning Components** is not available, kindly update your SharinPix package. You can refer to the following article for more information about how to update the SharinPix package:

[How to update SharinPix package from the AppExchange?](/faqs/how-to-update-sharinpix-package-from-the-appexchange.md)
{% 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/faqs/user-receiving-error-message-you-do-not-have-access-to-the-apex-class-named-sharinpixlightningcontro.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.