# Installation & Licenses Management Before you can access Avonni App Builder Components in Lightning App Builder, you need to install the package in your Salesforce org. ## Install from Salesforce AppExchange 1. **Navigate to AppExchange**: Go to [**Salesforce AppExchange**](https://appexchange.salesforce.com/appxListingDetail?listingId=2e584bb3-b5e0-415d-9347-d6567158d840\&channel=recommended) or click the App Launcher in Salesforce and search for "AppExchange" 2. **Find Avonni:** Search for "40+ App Builder & Sites Components" in the AppExchange marketplace 3. **Install the Package**: Click "Get It Now" and follow the installation prompts 4. **Choose Installation Options**: * Install for Admins Only (recommended for initial setup) * Install for All Users (after testing and configuration) 5. **Complete Installation**: Review and accept the package permissions, then click "Install" Install the Components {% hint style="danger" %} #### Important Requirement [**Enable Lightning Web Security**](https://developer.salesforce.com/docs/platform/lightning-components-security/guide/lws-enable.html) in your org before installing the Avonni Dynamic Components package—installation will fail without it. {% endhint %} *** ## Post-Installation Setup ### **Assign Licenses** After installation, assign licenses to users who will interact with the components: 1. Go to **Setup > Installed Packages** 2. Find "Avonni Experience Components" and click "Manage Licenses" 3. Assign licenses to appropriate users ### **Configure Permissions Sets** Assign the appropriate permission sets based on user roles: #### **Avonni Experiences Admin** * **Who needs it**: Administrators and builders who will add and configure Avonni components in Lightning App Builder or create Dynamic Components. {% hint style="warning" %} #### Important Access Requirements **For Non-Admin Users Adding App Builder Components** * Users need Lightning App Builder access in their profile or through an additional permission set * The Avonni Experiences Admin permission set alone is not sufficient * Without Lightning App Builder access, users cannot add or configure Avonni components on pages **Summary** * **App Builder Components only** → Need Lightning App Builder access + Avonni Experiences Admin {% endhint %} #### **Avonni Dynamic Components User** * **Who needs it**: End users who will view and interact with Dynamic Components that have been added to Lightning pages or an Experience Sites. * **What it allows**: Interaction with pre-configured Dynamic Components. #### **Avonni Experience Cloud Components User** * **Who needs it**: External users accessing Experience Cloud sites (community or portal users) * **What it allows**: Interaction with Avonni components placed on Experience Sites pages #### Permission Set Assignment Steps 1. Go to **Setup > Permission Sets** 2. Select the appropriate permission set from the list below 3. Click **Manage Assignments** 4. Click **Add Assignments** 5. Select users who need access 6. Click **Assign** **Key Reminder**: The Experiences Admin permission set provides configuration access but does not automatically grant Lightning App Builder access. Ensure users have the necessary profile permissions or additional permission sets to access Lightning App Builder.
### Verify Installation Once installed, verify the package is working correctly: 1. Navigate to **Setup > Lightning App Builder** 2. Edit any Lightning page 3. Look for components starting with "AX -" in the Custom Components section If you see the Avonni components listed, installation was successful, and you're ready to begin building enhanced Lightning pages. ### **Need Help with Installation?** If you encounter issues during installation or setup: * Check our installation troubleshooting guide for common solutions * Join our [**Trailblazer Community Group**](https://trailhead.salesforce.com/trailblazer-community/groups/0F9KX000000iFxO0AU?tab=discussion\&sort=LAST_MODIFIED_DATE_DESC) where other admins share their installation experiences and solutions * Contact our support team at Many installation questions have already been answered in the community, including permission set configurations, Lightning Web Security setup, and license assignment best practices. Search the group or post your specific question to get help from both our team and experienced Avonni admins.
Package Compatibility Notice **If you have existing Avonni packages installed** (Dynamic Components or Experience Sites), installing the Avonni Experience Components package will not cause conflicts, but there are essential details to understand: **Dynamic Components Duplication** * The Dynamic Components app will appear twice in your org, each with a different namespace. * Both versions will function independently without interference * Custom metadata will show Dynamic Components twice, but each serves its specific purpose * Your existing Dynamic Components functionality remains unchanged **Experience Sites Components Duplication** * Experience Sites components will be duplicated with distinct naming conventions * Components from the Avonni Experience Components package will be prefixed with "AX -" (e.g., "AX - Data Table") * Components from the original Experience Sites package retain their original names * This naming distinction prevents confusion when selecting components **No Impact on Performance** * Multiple package installations do not affect org performance or functionality * Each package operates within its own namespace * Users can continue using existing components without disruption This duplication is by design to ensure compatibility across different Avonni product lines while maintaining clear component identification for administrators and developers.
--- # Agent Instructions: 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: ``` GET https://docs.avonnicomponents.com/app-builder-components/getting-started/installation-and-licenses-management.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.