> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions/application-access-features.md). # Application Access Features This page is a companion to [Users and Permissions](/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions.md). That page explains the two layers of permissions: **Application access** and **Data permissions**. This page lists each feature in the **Application access** table, the part of Limio that it controls, and the documentation for that part of Limio. A feature shows a part of the app. The data permissions in the table decide what the user can do with the records in that part. For example, a role with the "Promo Codes" feature and no **Can Read** on promo codes sees the Promo Codes page, but no promo codes on it. ## Catalog | Feature | What it controls | Related data permissions | Documentation | | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Pages & Campaigns** | The **Pages** menu item in the Catalog, and the page builder. | Campaign, Page, Page Version, Build | [Page Builder Overview](https://docs.limio.com/product/page-builder/page-builder-overview-of-key-features) | | **Offers, Add-Ons, Tags, Segments, Assets & Entitlements** | The **Offers**, **Add-Ons**, **Discounts**, **Entitlements**, **Segments**, **Tags** and **Assets** menu items in the Catalog. | Offer, Add-On, Tag, Segment, Asset, Entitlement, Discount, Coupon, Plan, Product | [Offers](https://docs.limio.com/product/pricing/what-are-offers-and-how-to-configure-them), [Add-ons](https://docs.limio.com/product/pricing/what-are-add-ons-and-how-to-configure-them), [Entitlements](https://docs.limio.com/product/pricing/how-to-create-and-propagate-entitlements-with-limio) | | **Promo Codes** | The **Promo Codes** menu item in the Catalog. | Promo Code | [Promo Codes v2](https://docs.limio.com/product/pricing/how-to-configure-and-implement-promo-codes), [Discounts & Promo Codes](https://docs.limio.com/product/pricing/discounts-and-promo-codes) | | **Journeys** | The **Journeys** menu item in the Catalog. | Journey | [What are Limio Journeys](https://docs.limio.com/product/journey/what-are-limio-journeys) | | **Product Catalog** | The **Products** menu item in the Catalog. | Product | [Sync Between Limio and Zuora Catalogs](https://docs.limio.com/integrations/keeping-zuora-and-limio-in-sync/sync-between-limio-catalog-and-zuora-catalog) | | **Publishing & Unpublishing** | The **Publish** and **Unpublish** buttons on a catalog item and in its Builds panel. | None | [Publish/Unpublish Pages](https://docs.limio.com/product/page-builder/how-to-publishunpublish-your-pages-online), [Manage Versions with Publish](https://docs.limio.com/product/pricing/how-to-manage-offers-and-add-ons-versions-with-publish) | | **Campaign Approval** | The **Approve** button on a campaign. | None | | | **Export Data** | The **Export** button on catalog tables, and **Export** in the **Operations** area. | None | [Export](https://docs.limio.com/product/pricing/how-to-create-offers-and-add-ons-to-attach-to-pages/how-to-export-your-filtered-pages-offers-add-ons-or-products) | | **One-click Catalog Creation** | **Catalog Creation** in the **Operations** area. | None | | | **Catalog Sync** | The sync button for the product catalog in the **Operations** area. This button starts a sync from your billing system. | Product | [Sync Between Limio and Zuora Catalogs](https://docs.limio.com/integrations/keeping-zuora-and-limio-in-sync/sync-between-limio-catalog-and-zuora-catalog) | The **Operations** menu item shows when the user has one or more of **Export Data**, **One-click Catalog Creation** and **Catalog Sync**. ## Subscriptions and Analytics | Feature | What it controls | Related data permissions | Documentation | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Subscriptions Application** | The **Subscriptions** application: **Customers**, **Subscriptions**, **Orders**, **Baskets**, **Events**, **Webhooks** and **Gift Codes**. | Subscription, Customer, Order, Basket, Event, Identity, Payment Method, Webhook, Gift Code, Address, and the other subscription records | | | **Forget Customer Data (GDPR)** | The erasure of the personal data of a customer. The user also needs **Subscriptions Application**. You cannot undo an erasure. | None | [Erase Personal Data (GDPR)](https://docs.limio.com/guides/administration-guides/how-to-erase-personal-data-for-data-privacy-requests) | | **Analytics** | The **Analytics** application: **Orders**, **Cancels & Saves**, **Switch Orders** and **Checkout Conversion**. It also controls the export of analytics data. | None | [Limio Analytics Overview](https://docs.limio.com/product/analytics/limio-commerce-analytics) | ## AI | Feature | What it controls | Related data permissions | Documentation | | ------------- | ---------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------------------------------------------------------------------------------- | | **AI Agents** | The **AI (Beta)** application: **Agents**, **Connectors**, **Knowledge**, **Visitors**, **Conversations** and **Workflows**. | Agent, Knowledge Doc, Toolset | [Limio Agents Overview](https://docs.limio.com/agents/limio-agents/limio-agents) | ## Administration | Feature | What it controls | Related data permissions | Documentation | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **General Settings** | The **General Settings**, **Allowed Hosts** and **Order Processing** settings pages, and the `robots.txt` file of the shop. | Config | [Config Settings](https://docs.limio.com/product/settings/config-settings), [Add robots.txt File](https://docs.limio.com/product/seo/how-to-add-a-robotstxt-file) | | **Developer Credentials** | **Developer Credentials** in the user profile. The user can create and delete API credentials. | None | [OAuth Bearer Token](https://docs.limio.com/developers/api-documentation/authentication-overview/oauth-bearer-token) | | **User Management** | The **Users** and **Create User** pages: the user list, new users, password resets, and removal of users. To change the role of a user, the role also needs **Can Write** on the **Users** record type. | Users | [Users and Permissions](/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions.md), [Set Up a New User](/support/user-permissions-and-administration/how-to-set-up-a-new-user.md) | | **Roles & Permissions** | Changes on the **Permissions** tab. Without this feature, the **Permissions** tab is read-only. | None | [Users and Permissions](/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions.md) | | **Impersonate Shop Customer** | Access to the shop as a specific customer, to see the pages that customer sees after login. This feature has no page in the app. It applies to the API only. | None | | | **Partner Management** | **Partners** in the user profile, where you manage partner organisations and partner users. | Partner Org, Partner User | [Creating and Managing Partners](https://docs.limio.com/product/partner-portal/creating-and-managing-partners) | ## Roles from before release 118 Release 118 converts each existing role to the two-layer model. The converted role keeps the access it had before, with one exception: **no role can delete records after the change**. To let a role delete records of a type, turn on **Can Delete** for that record type. Before release 118, five features did not have a toggle of their own. They came with a different permission, and a converted role keeps them: * **Forget Customer Data (GDPR)** came with edit access to subscriptions. * **Roles & Permissions**, **Impersonate Shop Customer** and **Developer Credentials** came with edit access to users. * **Catalog Sync** came with edit access to the product catalog. After the change, you can turn each of these features on or off without a change to the other permissions of the role. --- # 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.limio.com/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions/application-access-features.md?ask=&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.