Foxit Admin Console is Foxit’s portal for managing licences, users and software updates for Foxit PDF Editor, Foxit eSign and the AI Assistant across an organisation. Foxit offers it as a cloud service hosted on AWS or as an on-premise installation.[2] It sits on top of the activation mechanisms built into Foxit software. Subscription releases of PDF Editor activate when the user signs in to a Foxit account. Perpetual releases activate with a registration key. Installations managed by Admin Console activate according to the mode the administrator chooses.[3] For a software asset manager, these mechanisms are both the enforcement point for Foxit’s per-user and per-computer licences and the main source of usage evidence. For the overview, see Foxit licensing.
Editions
| Mechanism | Applies to | How a seat is consumed |
|---|---|---|
| Foxit account sign-in | Subscription Release of PDF Editor; mobile subscriptions | Signing in activates the product; activating another device deactivates the original[3][4] |
| Registration key (key code or key file) | Perpetual Release; key-licensed mobile installs | Entering the key activates the computer; Help > Deactivate releases it[3][4][10] |
| Admin Console Account Mode | Organisations using Admin Console Cloud or On-Premise | Licences assigned to users; users activate by signing in[1] |
| MSI KEYCODE / KEYPATH | Scripted Windows deployment | The installer activates with a key code or saves a licence key file[5] |
Foxit’s documents describe Admin Console’s price in three ways. The product page FAQ says it is “a free feature available for Foxit PDF Editor, Foxit eSign, and AI Assistant plans”.[2] The PDF Editor pricing FAQ says Admin Console is “sold separately”.[7] The EULA says Admin Console obtained with perpetual licences before 2024-06-20 continues at no charge, and that later purchases carry a yearly subscription charge.[6] Customers should check the order to see whether Admin Console is included. Catalog: Admin Console described as free within PDF Editor, eSign and AI Assistant plans; Admin Console with perpetual licences: yearly charge for purchases after 2024-06-20.
Metrics
Admin Console does not create a metric of its own. It administers the metrics of the products it manages. The License Management page shows active users and licence usage for each product, and lets administrators assign, change and unassign licences.[1] For PDF Editor it counts subscription users and the devices each user activates, up to the Permitted Number of Computers. For Foxit eSign it counts licensed users and pre-purchased envelopes. Enterprises may buy a set number of envelopes for a set number of users.[1] For the AI Assistant it pools paid AI credits. When several AI Assistant licences are managed through Admin Console, the 2,000 monthly credits of each licence combine into one shared pool that administrators allocate. Free credits stay individual.[8] Catalog: Paid AI credits pool across a team through Admin Console; free credits do not.
Counting / floors
Account Mode and authorization models. Admin Console manages PDF Editor licences in Account Mode. Each end user activates PDF Editor by signing in, and administrators control who may activate and which edition.[1] Two authorization models are available:
- Manual authorization (the default). Only users who have been assigned a licence can activate.[1]
- Automatically authorize. Any user who signs in can activate while licences remain available. The administrator can limit this with rules based on SAML attributes.[1]
When a licence is unassigned, the user can no longer activate Foxit applications by signing in.[1] Catalog: Account Mode: only users with assigned licences (or auto-authorized users) can activate.
Devices per user. When assigning a licence, an administrator can choose which licence order it comes from. The administrator can also set its expiration time and the maximum number of devices that may log in to activate the product. If no value is set, the user gets the available licence with the longest validity period. The user may then activate on up to the maximum number of devices that the product plan permits.[1] Neither the EULA nor the public pricing pages state that plan maximum. It is the “Permitted Number” of the EULA, set per order.[6] Catalog: Admin Console can cap devices per assigned user.
Quotas. Super and system administrators can set licence quotas for first-level organisational units, which caps what each product administrator may assign. Without a quota, assignments are unlimited but should not exceed the total number of licences available.[1] Catalog: License quotas per OU cannot exceed the total licences.
Licence priority. Where a user holds several licences for the same product, or licences with different expiry dates, administrators can set the order in which licences are consumed. Otherwise clients follow a default authorization order.[1]
Mobility, offline use and reclamation
Moving a licence. Outside Admin Console, a subscriber moves a licence by signing in and activating a new device. This automatically deactivates the original one. A perpetual user chooses Help > Deactivate before activating elsewhere.[4] Subscription licensees can also disable current activations by signing in to their Foxit accounts.[11] Users managed by Admin Console remove a device’s authorization under Help > Manage.[4] On mobile, devices are removed from the account’s device list, or deactivated through Help > Deactivate for key-code activations.[10] Catalog: Deactivation frees an activation for another device.
Restore activation. Some licences allow activation on only one device. If such a device breaks, an administrator can restore the activation so the user can sign in and activate on a replacement.[1] Catalog: Restore activation for single-device licences.
Offline period. Administrators set how long PDF Editor may be used offline. A device that has not connected to the Admin Console server within that period is deactivated automatically. It can reactivate when it reconnects, unless the licence has been revoked or has expired. The default is 14 days.[1]
Automatic deactivation. Optionally, licences are revoked from users who have not launched PDF Editor for a set number of days, with a minimum of 90. Users can be warned in advance, and administrators notified after revocation. Revoked users are not reassigned licences automatically until an administrator restores them.[1] Catalog: Admin Console offline period (default 14 days) and automatic licence revocation (minimum 90 days).
Network restriction. Administrators can allow activation only from specified MAC addresses, and only from clients in specified IP and MAC ranges.[1]
Virtualization & partitioning
Admin Console has no virtualization rules of its own. The licence it manages does. A single-user licence may run on one virtual machine for its user, but the VM may not be copied or shared without consent. Terminal servers need a multi-user or site licence.[6] Foxit’s deployment guide lists PDF Editor as verified Citrix Ready with Citrix XenApp 7.13.[5] That is a technical compatibility statement, not a licence grant.
Cloud / BYOL
Admin Console Cloud is hosted on AWS by Foxit. Admin Console On-Premise is self-hosted. Both support SSO, delegated administrator roles and reporting.[2] The on-premise edition can push desktop updates from Foxit servers to the customer’s own servers.[9] A user can reach products only if the user’s Country/Region matches the data centre of the organisation’s Admin Console. Changing a user’s data centre automatically revokes that user’s previously assigned licences.[1]
Deployment
The 2026.2 deployment guide for Foxit PDF Editor for Windows documents several activation options. The EXE installer has a /keycode switch. The MSI has KEYCODE, which activates with a key code, and KEYPATH, which saves a licence key file to the installation folder.[5] The Foxit Customization Wizard can “license the product on a volume scale”, so each copy does not need to be registered individually.[5] Group Policy settings for the Perpetual Release can force the activation dialog at launch. They can show registration-code input, Admin Console sign-in or both, and can point clients at the organisation’s Admin Console server.[5] Catalog: Volume deployment can pre-activate installers with a key code or key file.
A key code embedded in an installer image is easy to over-deploy. The EULA counts activations against the Permitted Number of computers whatever the deployment method.[6] Volume deployments therefore need the same reconciliation as individually activated copies.
Reporting and audit evidence
Admin Console’s Reports page shows total, assigned and activated licences, active users, usage per organisational unit or group, and OU quotas, for each product.[1] The Usage Details tab exports user names, email addresses, licence information, and MAC and IP addresses. The User Activity tab shows activation time, days since active, last login and an inactivity filter.[1] Admin roles include License, Report and Auditor administrators.[2]
These reports answer the EULA compliance clause. On request, a business must document and certify within 30 days that its use of Foxit Products matches its licences. Foxit may inspect records, systems and worksite, and a customer found non-compliant pays for the additional licences and the inspection.[6] An export of assigned and activated licences, compared with order quantities, is the natural basis for that certification. Perpetual keys activated outside Admin Console must be added to it separately. See license compliance. Catalog: Business customers must certify compliance within 30 days and allow inspection.
Out of scope
- Admin Console On-Premise installation, updates and server sizing.
- Foxit eSign account settings beyond licence assignment, covered in Foxit eSign, AI Assistant and services licensing.
- macOS deployment tooling and Microsoft Intune packaging steps, which do not change licence rules.