> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/choosing-the-right-components/installation-and-package.md). # Installation & Package Five component lines, three packages, one install flow. Start with the package that matches where you build today, and add the others whenever you need them. ## One suite, three installs The Avonni suite ships as three managed packages instead of one large library, so your org only carries what you actually use. This is not a fork in the road. The three packages are independent, they coexist in the same org without conflict, and most teams end up with more than one. | Package | What it adds | Where you build | | --------------------------------- | ----------------------------------------------------- | ----------------------------------------------------------------- | | **Avonni Experience Components** | App Builder, Dynamic, and Experience Sites components | Lightning pages, record pages, Home pages, Experience Cloud sites | | **Avonni Flow Screen Components** | 70+ components made for Screen Flows | Flow Builder | | **Avonni LWC Components** | 55+ `avonni-*` building blocks | Your own Lightning Web Components | {% hint style="success" %} #### Not sure where to start? Install **Avonni Experience Components** first. It covers three of the five component lines and the widest range of Salesforce surfaces. Add the Flow package the day you build your first wizard, and the LWC package the day a developer joins the project. Nothing you install now blocks anything you add later. {% endhint %} *** ## Avonni Experience Components Best for Lightning pages, dashboards, record pages, and Experience Cloud sites. One install delivers three component lines: * **App Builder Components**: quick, standard layouts and dashboards, dragged straight onto a Lightning page. * **Dynamic Components**: advanced UI logic, formulas, and reactive interfaces, the closest thing to custom development without code. * **Experience Sites Components**: branded customer and partner portals on Experience Cloud. They are always on. They live on the page layout, they react to each other and to record changes, and nobody has to launch a flow to see them. Install Avonni Experience Components Documentation: [App Builder Components](https://docs.avonnicomponents.com/app-builder-components) · [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components) · [Experience Sites Components](https://docs.avonnicomponents.com/experience-cloud) *** ## Avonni Flow Screen Components Best for wizards, forms, and guided processes. This package is built for the Flow Builder. It adds more than 70 components that live inside your Flow variables, so a screen flow can collect, display, and validate data that standard Flow screen components cannot handle. * Specialized inputs, choices, and layout components for Flow screens. * Deep integration with Flow logic, formulas, and automation. * Multi step processes as a core feature, not a workaround. Install Avonni Flow Screen Components Documentation: [Flow Screen Components](https://docs.avonnicomponents.com/flow) *** ## Avonni LWC Components Best for developers writing their own Lightning Web Components. This package is a code library, not a builder. You get production ready building blocks instead of starting from scratch: 55+ components you reference with `avonni-*` tags, exactly like the standard `lightning-*` ones. * **43 Core Components**: presentational building blocks such as Avatar, Combobox, Layout, Progress Bar, and Visual Picker. * **12 Data Driven Components**: components that query records themselves, such as Data Table, Kanban, Scheduler, Map, and Pivot Table. A full data table is about 30 lines of configuration with no Apex controller behind it. * Zero Apex for the data display layer. Query mode handles fetching, search, sort, filter, and pagination. Install Avonni LWC Components Documentation: [LWC Components](https://docs.avonnicomponents.com/lwc-components) *** ## Installing a package Whichever package you install, the sequence is the same, and it takes about five minutes: run the install, assign the license, assign the permission set. {% stepper %} {% step %} ### Check the prerequisite The **Experience Components** and **Flow Screen Components** packages require Lightning Web Security. In **Setup**, search for **Session Settings**, tick **Use Lightning Web Security for Lightning web components and Aura components**, then save. If an install fails with an error mentioning `LWC1503: Dynamic imports are not allowed`, this setting is the cause. Enable it and run the install again. {% endstep %} {% step %} ### Run the install Use one of the buttons above, or the direct install links published with every version in the [Release Notes](https://docs.avonnicomponents.com/changelog). Install in a sandbox first, then in production. **Install for Admins Only** is the safe choice for a first pass; you can widen it later. {% endstep %} {% step %} ### Assign the package license Go to **Setup > Installed Packages**, find the Avonni package, click **Manage Licenses**, then **Add Users**. The license gives a user a seat. {% endstep %} {% step %} ### Assign the permission set Go to **Setup > Permission Sets**, open the Avonni permission set, then **Manage Assignments > Add Assignments**. Pick the same users you licensed. The permission set gives them the technical rights to load the components and fetch data. {% endstep %} {% endstepper %} {% hint style="warning" %} #### A license on its own is not enough A user who has a license but no permission set sees errors instead of components, and a user with the permission set but no license sees nothing at all. Both steps are required, for every user. {% endhint %} Step by step instructions with screenshots, per package: | Package | Detailed installation guide | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Avonni Experience Components | [Dynamic Components](https://docs.avonnicomponents.com/dynamic-components/getting-started/installation-and-licenses-management) · [App Builder Components](https://docs.avonnicomponents.com/app-builder-components/getting-started/installation-and-licenses-management) | | Avonni Flow Screen Components | [Installation & Licenses management](https://docs.avonnicomponents.com/flow/getting-started/installation-and-licenses-management) | | Avonni LWC Components | [Installation & Licenses Management](https://docs.avonnicomponents.com/lwc-components/getting-started/installation-and-licenses-management) | *** ## Licenses * **Sandbox**: the install includes a site license. Unlimited users, no time limit, so you can build and test freely before anyone signs anything. * **Production**: installs of Avonni Experience Components and Avonni Flow Screen Components include a Freemium plan with 10 licenses. For more seats, write to . *** ## Staying up to date Updates are not automatic. Each release is a new version of the package that you install when you are ready, so a release never changes your org behind your back. The [Release Notes](https://docs.avonnicomponents.com/changelog) always show the current version and carry its install links for sandbox and production. Install in a sandbox, check your pages and flows there, then run the production link. *** ## Frequently asked questions
Can I install more than one package? Yes, and many teams do. If you build Lightning pages, screen flows, and custom LWC, the three packages coexist without conflict. Install whichever combination matches your team, in any order.
Do I have to uninstall anything before adding a package? No. Adding a package never replaces or degrades one you already have. Installing Avonni Experience Components alongside the Flow package extends what you can build; it does not change how your existing flows behave.
Do they work in sandboxes? Yes. All packages are fully compatible with sandbox environments, and a sandbox install includes a site license, so you can test with as many users as you like.
I installed Avonni Experience Components but I cannot find Dynamic Components in Installed Packages. That is expected. **Setup > Installed Packages** shows a single entry, **Avonni Experience Components**, and that one package delivers the App Builder, Dynamic, and Experience Sites component lines. If you are still on the legacy standalone package, the entry is named **Avonni Dynamic Component**, in the singular.
A user cannot see the components. What did I miss? Almost always the second half of the access model. Check that the user has both the package license (**Setup > Installed Packages > Manage Licenses**) and the Avonni permission set (**Setup > Permission Sets**). One without the other does not work.
Which package should I start with? If you have no strong preference, start with **Avonni Experience Components**: it covers the most ground. If your next project is a guided process, start with the **Flow Screen Components** package. If your team writes its own Lightning Web Components, start with **LWC Components**. None of these choices closes a door.
{% hint style="info" %} Still weighing the component lines rather than the packages? The [Selection Guide](https://docs.avonnicomponents.com/choosing-the-right-components/selection-guide) walks you through the choice, and the [Feature Comparison](https://docs.avonnicomponents.com/choosing-the-right-components/feature-comparison) puts every capability side by side. {% 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.avonnicomponents.com/choosing-the-right-components/installation-and-package.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.