> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/integrations-and-data-exchange/custom-fields/permissions.md).

# Permissions

Custom Fields have their own permission, visible in the role permission list once the feature is enabled for your instance. It controls the **schema** (groups and fields) — not whether a user can enter values on a member, campaign, or reward form.

<table><thead><tr><th width="168.83984375">Permission level</th><th>Effect</th></tr></thead><tbody><tr><td><strong>No access</strong></td><td>The <strong>Custom Fields</strong> item is hidden from the side menu, and the schema screens can't be reached by URL. Values are still visible and editable on the Member / Direct / Automation / Referral / Challenge / Leaderboard / Fortune Wheel / Reward forms.</td></tr><tr><td><strong>View</strong></td><td>The schema editor is read-only — all fields and buttons are disabled, and the summary step can't be reached. Values on entity forms remain editable.</td></tr><tr><td><strong>View + Modify</strong></td><td>Full management of the schema — create, edit, activate/deactivate, and delete groups and fields.</td></tr></tbody></table>

{% hint style="info" %}
**Managing the schema and filling in values are two separate permissions.** A user without any access to the Custom Fields module can still enter and update values on member and campaign forms, as long as they have the underlying Member/Campaign/Reward permission.
{% endhint %}

For the full permission list, see [Available Permissions (ACL)](/implementation-guide/administration/settings/roles/available-permissions-acl.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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/integrations-and-data-exchange/custom-fields/permissions.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 `build a script that syncs our docs to a CMS` 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.