AX - Button

AX - Button is an Experience Cloud component that creates clickable buttons on Experience Sites pages to trigger actions like navigation, form submissions, record creation, or opening modals.

Use it to add custom calls-to-action, submit forms, navigate to specific pages, create records, or trigger flows. Configure the button's label, styling, icon, and action in Experience Builder without code.

Perfect for portal CTAs, custom navigation, "Contact Us" actions, record creation workflows, or any user interaction that needs a clear, branded button.

After dragging AX - Button onto your page in Experience Builder, you'll configure two main things: how the button looks and what happens when users click it (see Interactions).

These settings control how your button looks on the page.

Label is the text displayed on the button. Keep it concise and action-oriented (e.g., "Submit Request," "View Details," "Contact Us").

Icon Name adds an icon next to the label to help users quickly understand the action. Choose from Salesforce's icon library—common choices include utility:download for downloads or utility:email for contact actions. Icon Position places the icon to the left or right of the label; left works well for most cases, while right can indicate forward navigation.

Variant is the button's visual style: base, neutral, brand, brand-outline, border, border-filled, border-inverse, bare, bare-inverse, inverse, container, success, destructive, or destructive-text. Choose one that suits the importance of the action and the design language of the page.

Horizontal Alignment positions the button within its container—left, center, or right. Center works well for standalone CTAs, while left suits form buttons.

Stretch expands the button to fill the full width of its container — use it for prominent CTAs or to match the width of form fields above it.

Disabled prevents users from clicking the button. Use it when an action isn't available yet, such as a "Submit" button awaiting required fields.

Title sets tooltip text shown when hovering over the button, and Alternative Text provides accessible text describing the button when it shows only an icon.

CMS Document Download and Document URL or Expression Download make the button download a file when clicked — reference a CMS document or provide a direct URL instead of triggering an interaction.

The Link To setting determines what happens when users click the button. Choose the action type that matches what you want to accomplish.

Displays a brief notification message that appears at the top of the page and disappears after a few seconds.

When to use it: Confirmation messages like "Changes saved" or "Request submitted" that don't require user action. Toasts provide feedback without interrupting the user's workflow.

Redirects users to another page—either within your Experience Site or an external URL.

When to use it: "Learn More" buttons that go to detail pages, "Back to Home" navigation, or links to external resources. You can navigate to standard pages, record pages, or custom URLs.

Opens a popup window with a message that users must acknowledge before continuing.

When to use it: Important notices that users need to read, like terms and conditions, privacy disclosures, or warnings before they proceed with an action.

Displays a confirmation dialog asking users to confirm or cancel their action.

When to use it: Actions with consequences that can't be undone, like deleting a record, canceling a submission, or removing access. The dialog gives users a chance to reconsider before proceeding.

Launches a Salesforce Flow in a popup modal window.

When to use it: Multi-step processes like submitting a support case, completing a survey, updating account information, or any guided workflow. Build the flow in Flow Builder, then connect it to the button—the flow runs inside the modal without navigating away from the current page

Customize the button's appearance from the Style section of the property editor.