> For the complete documentation index, see [llms.txt](https://docs.stacksync.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacksync.com/two-way-sync/connectors/salesforce/make-custom-fields-visible.md).
# Make Custom Fields Visible
When a custom field is created, it’s not visible by default to all profiles in the Salesforce organization. Users with different roles won’t be able to see the newly created custom field.
You need to modify the Field-Level Security settings after the custom field is created to allow other Salesforce profiles to see it. Stacksync enables Custom Field Visibility for the following profiles:
* System Administrator
* Standard User
{% hint style="info" %}
**How to enable a custom field for other profiles:**
1. Click on `Setup`\
2. Go to `Object Manager`
3. Select the related Object
4. Select `Fields & Relationships`
5. Select the `Custom Field`
6. Select Field-Level Security and make it visible to the user groups you want
**To make the custom Field visible in a layout:**
1. Click on `Setup`\
2. Go to `Object Manager`\
3. Select the related Object\
4. Go to the Page Layout section\
5. Select and edit the layout where you want to include the custom field you just created.\
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.stacksync.com/two-way-sync/connectors/salesforce/make-custom-fields-visible.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.