Get an overview of Foxit PDF Editor's licensing methods to deploy licenses to activate and authenticate Foxit products.
Audience:Organizations looking to customize Foxit PDF Editor before deploying it to their knowledge workers.
In this article:
- Named User licensing
- Shared Device licensing
- Registration Code licensing
Named User licensing (available in perpetual or subscription)
Named user licensing is the default and most popular licensing method to deploy and use Foxit products and services. Designed for the network-connected scenario where app licenses are managed based on individual user need for use of the app.
Named User Licensing ties the usage of Foxit apps and services to an individual user. Named User Licensing provides IT admins complete control to add and remove product licenses for a user at any time. It also facilitates better compliance tracking as IT admins don't need to track machines, and can manage licenses centrally.
Named licenses require periodic Internet connectivity. Computers must connect to Foxit servers for initial activation, and then at least once every 90 days.
End users can sign in with their credentials to access the apps and services. You can also configure SSO to enable seamless access and experience as the rest of your enterprise apps.
Benefits of Named User Licensing:
For end users:
- Access to all Foxit productivity apps: Including the latest cloud first applications such as Foxit PDF Editor for Cloud, Foxit eSign and Foxit PDF Editor for Cloud Microsoft Teams. These applications are not available with any other licensing method.
- Access to Foxit Cloud services: Automate signature driven workflows and deliver a faster return on signed documents with Foxit eSign. Collaborate on PDFs using our Microsoft Teams app.
- Enhanced security and control: Get enterprise-level security with advanced user identity management, including Single Sign-On (SSO), and protect assets with at-rest and in-transit encryption.
- License management: Easily manage users and deploy apps throughout your organization.
Deploying apps using Named User licensing
There is no requirement to pre-configure computers for Named User Licensing. Foxit productivity apps will only need to be installed or deployed on the end-user computers. Each of the computers to be licensed must have access to the Internet. However, access to the Internet can be controlled by a firewall device that intercepts and unpacks all network traffic to verify its content and ensure that:
no unauthorized data is sent outside the internal network
all transmitted data is sealed inside an encrypted tunnel between the firewall device and the Foxit servers
the endpoint of every transmission is an authorized Foxit server with a known network address and a publicly signed, non-revoked SSL certificate
End-user sign-in workflow
On launching an app, a sign-in screen display. End users can sign in with their credentials to license the app. If a user is not entitled to that particular app it will run as a trial but will stop working once the trial period expires.
Shared Device Licensing
Shared Device License is a licensing method for both Foxit PDF Editor for Windows & MacOS; however, it is only available for educational institutions where software is assigned to a device instead of an individual.
Shared Device Licensing is ideal for desktop computer labs and classrooms. For example, you can install Foxit PDF Editor in your computer labs to allows students and teachers, with access to these computers, to use Foxit PDF Editor as part of your license agreement with Foxit.
• Shared Device License is only applicable to educational institutes.
• Shared Device License can be used in classrooms and labs on shared computers.
• Only subscription license can be used as a Shared Device License.
• One-time (perpetual) cannot be used as Shared Device License.
In addition, the relevant interpretation rights belong to Foxit.
Registration Code Licensing (available in perpetual or subscription)
This licensing method is suitable for a very small number of customers and, as with named licensing, can be used to create pre-licensed packages that are deployed remotely.