> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/profiles-and-permissions/access-levels-for-permissions.md).

# Permission Levels & Record Access

A profile's permissions are set per resource and combine three controls.

## Navigation visibility

Each **navigation group** (CRM, Commerce, Content, Rules & Automation, and so on) has a visibility toggle that controls whether it appears in the user's sidebar. Turn a group off to hide it entirely from that profile.

## Access level

For each resource within a group, choose how much the user can do:

* **View** — see existing records; no changes.
* **Edit** — view and modify records.

Some resources (such as the Dashboard) are view-only.

## Record access scope

For record-based resources, set *which* records the user can act on:

* **All records** — every record in the tenant.
* **Created by them** — only records the user created.
* **Created or assigned to them** — records the user created or that are assigned to them.

Record scope is how you keep a CSR or partner limited to their own book of business while still giving them Edit access to the records they own.


---

# 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.peakcommerce.com/product/using-peakcommerce/profiles-and-permissions/access-levels-for-permissions.md?ask=<question>&goal=<endgoal>
```

`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.