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

Important Requirement

Enable Lightning Web Security in your org before installing the Avonni Dynamic Components package—installation will fail without it.

---

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.

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

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.

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.