> 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/user-profile-overview.md). # Profiles Overview A **profile** defines the detailed permissions a user has — which parts of the platform they can see, which records they can view or edit, and the scope of records they can act on. Every user is assigned one profile in addition to their [role](/product/using-peakcommerce/users-and-user-roles/user-roles.md): the role sets the broad experience, and the profile fine-tunes it. ## Why profiles Profiles let you express permission tiers without code. Common patterns: * **Tiered staff** — CSR Junior (view + limited actions), CSR Senior, and CSR Supervisor (full subscription management). * **Scoped admins** — a Default Admin with minimal permissions versus a full Administrator with access to everything. * **Customer tiers** — a standard customer profile versus a read-only "managed customer" who can view subscriptions and pay invoices but not change plans. * **Partner access** — partner profiles scoped to their assigned accounts. ## How profiles work Each profile is tied to a **role type** (Admin, CSR, Partner, or Customer) and carries permissions across the platform's navigation groups (CRM, Commerce, Content, and so on). For each area you control: * **Navigation visibility** — whether the group appears in that user's sidebar. * **Resource access level** — View or Edit for each resource (Organizations, Orders, Subscriptions, Invoices, and so on). * **Record access scope** — all records, only records they created, or records created by or assigned to them. See [Permission Levels & Record Access](/product/using-peakcommerce/profiles-and-permissions/access-levels-for-permissions.md) for the full model, and [Creating a Profile](/product/using-peakcommerce/profiles-and-permissions/creating-a-profile.md) to build one. Manage profiles in **Settings → Profiles**, where each profile shows its role, how many users are assigned, and a summary of its permissions. --- # 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/user-profile-overview.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.