> 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/why-is-the-sharinpix-image-related-list-not-displaying-after-being-added-to-the-layout.md).

# Why is the SharinPix Image Related List not displaying after being added to the layout?

If the SharinPix Image Related List does not appear on the screen after you have added it to the layout, the most likely reason is insufficient field-level access.

**Possible Cause:**

* The lookup field linking the object to the [**SharinPix Image Object**](/documentation/image-sync/the-sharinpix-image-object.md) does not have the required access permissions.

**Solution:**

1. **Check Field-Level Security** :
   * Navigate to **Setup** → **Object Manager** → **SharinPix Image Object**.
   * Locate the lookup field related to your object.
   * Verify its **Field-Level Security** settings.
2. **Provide Minimum Read Access** :
   * Ensure that at least **Read** access is granted to the field for the relevant user profiles.

After updating the permissions, refresh your page and check if the related list is now visible.

{% hint style="success" %}
**Tips:**

* You can refer to the [**Setup SharinPix Image Sync**](/documentation/image-sync/setup-sharinpix-image-sync.md) Documentation for more information on its configuration.
* If the Related List is still not visible after providing access to the field, contact [**SharinPix Support**](/getting-started/how-to-contact-support.md) for further assistance.
  {% 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/why-is-the-sharinpix-image-related-list-not-displaying-after-being-added-to-the-layout.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.