Salesforce does not provide a direct way to determine whether a user has an Apsona license when configuring Lightning Component Visibility. As a result, Apsona licenses cannot be used directly as visibility filters for custom Apsona buttons on Salesforce record pages.
The recommended approach is to use Lightning Record Page Component Visibility Filters on the Apsona button component and control visibility through Salesforce Profiles or Permission Sets. Since users who have Apsona licenses are typically granted access to Apsona-related permissions (such as the Apsona Items object, Apsona Visualforce pages, or other Apsona-specific permissions), these profiles or permission sets can serve as a proxy for license-based visibility.
For example, the Apsona Doc Gen Button V2 component can be configured to display only for specific Salesforce Profiles or users assigned a designated Apsona Permission Set. To filter by profile, create an Advanced Visibility Filter using User → Profile → Name, set the operator to Equals, and specify the profile names that should have access to the button.
With this configuration, users assigned to the approved profiles or permission sets can see and use the button, while users without those assignments do not see it. This effectively replicates license-based visibility without requiring direct access to Apsona license information.
When controlling access to Apsona buttons, use Salesforce Profiles or Permission Sets associated with licensed users, as Apsona license assignments themselves are not available as Lightning Component Visibility criteria.