Your team, ready to work.

A desktop console for IT. A simple sign-in for everyone.

License Manager is a Windows desktop app backed by a service on your company server. Open it from the Start menu to manage people, seats and computers. Closing the window leaves licensing running.

1. 01Prepare server
2. 02Install manager
3. 03Connect purchase
4. 04Assign people
5. 05Share instructions

This guide covers License Manager 1.0 and company sign-in in PolyPDF 1.6 or later. Use the Teams-compatible desktop release supplied by IT. The License Manager belongs on the server; employees install PolyPDF on their own Mac or Windows computer.

One Teams seat covers one named employee on one active computer. An administrator does not need a seat just to manage the company. Personal licenses remain separate and keep their existing rights.

Choose your seats.

1. Open your Teams account. Choose at least 3 users with the slider or exact quantity field.
2. Verify the billing-owner email, enter your company name, and review the quote and Teams terms.
3. Complete payment. Return to your account and refresh purchases until the order is marked Paid and the purchased capacity is available.

100 seats cost $1,998 before tax. Add-on purchases also require at least 3 seats. Your resulting paid seat count determines the rate for newly purchased seats; earlier purchases are not repriced. Seats include perpetual PolyPDF 1.x use and all 1.x updates.

If payment is pending, wait and refresh; do not pay again. A return-page visit does not activate seats. Use Orders and receipts → View receipt / invoice for paid orders.

You’re ready when your account shows the paid seat capacity. Employee assignments happen in your company’s manager.

Have these details ready.

Windows host

Windows Server 2022 or 2025, x64, with local administrator access for setup. The installer includes its runtime; no development tools are needed.

Company address

A DNS hostname that resolves to the server and is reachable from employee computers, including over your VPN when required.

Trusted HTTPS

A matching certificate with its full intermediate chain and private key, both in PEM format. The server and employee computers must trust the issuing authority.

Sign-in method

Choose Microsoft Entra or local invitations. Microsoft mode needs one workforce tenant, a dedicated single-tenant application, a client secret, and the initial administrator’s user object ID. Local mode uses Windows administrator approval on the server and needs no Entra registration.

Network access

Inbound HTTPS on port 7444 from authorized company computers. Outbound HTTPS to www.polypdf.com for purchased-capacity validation. Microsoft mode also needs access to Microsoft Entra.

You’re ready when the hostname resolves, HTTPS can be trusted on every participating computer, and IT has chosen the sign-in method. Prepare Entra details only for Microsoft mode.

Install the console. Configure the server.

1. Run the signed Windows License Manager installer. Verify the publisher is Euclidean Software, LLC. Complete installation.
2. Open Start → PolyPDF Teams → License Manager, then choose Set up this server. Approve the Windows administrator prompt for the installed setup helper.
3. In Company server, enter the hostname without https://, a port or a path. Select the certificate chain and matching private key.
4. In Sign-in method, choose Microsoft Entra ID or Local invitations and computer approval. This choice is fixed for the installation; existing managers keep their current method.
5. For Microsoft mode, in Microsoft details, enter the tenant ID, client ID, administrator user object ID and client secret.
6. In Review & install, check the HTTPS address. For Microsoft mode, copy the Entra Web redirect URI and check it matches your registration. Local mode needs no callback registration. Choose Install manager.
7. When the console is ready, choose Sign in with Microsoft. Complete sign-in in the system browser, compare its code with the console’s code, then choose Open desktop console. Return to License Manager. For local mode, choose Continue with Windows administrator on the server, approve Windows elevation, and confirm the matching code in the approval dialog.

You can cancel setup and start it again from the console. An already configured server is detected automatically, so an upgrade does not require re-entering company credentials.

Microsoft mode uses the system browser for authentication and confirmation. Local administration uses Windows approval on the company server; local employees use their browser to request computer approval. Day-to-day administration stays in the desktop console. A company HTTPS address connects the console and employees to the background service.

You’re ready when the desktop console opens People & licenses. A new manager shows 0 purchased seats until you connect your purchase.

Connect your purchased seats.

1. In License Manager, open Service health and choose Copy public key.
2. The billing owner opens the correct company in the Teams account, expands Connect an installed manager, and pastes that public key.
3. Choose Generate enrollment code. Copy the code and paste it into Enrollment code in the manager’s Service health screen.
4. Choose Enroll manager. Check that the purchased capacity appears in People & licenses.

Enrollment codes expire after ten minutes and work once. If a code expires, generate another for the same manager public key; the previous code stops working. Keep enrollment codes private.

One manager can be active per company. Use Replace your license manager only when intentionally moving to another manager, and review the replacement confirmation.

You’re ready when the manager shows the correct purchased capacity and Service health reports validated authorization.

Assign people, then share the connection file.

1. Open People & licenses. For Microsoft mode, use the employee’s immutable Entra user object ID. For local mode, enter their name and a stable employee ID; the console can generate this ID for you. Choose Download CSV template for a larger team.
2. For Microsoft mode, populate objectId. For local mode, populate employeeId and displayName; reuse the same employee ID for later updates. Both modes accept optional email and assign (true or false); displayName is optional only in Microsoft mode. Review the import preview and correct invalid or duplicate rows before applying.
3. Choose Assign seat for each person who needs Pro access. In Microsoft mode, unassigned sign-ins appear as pending requests; an email domain never grants a license.
4. Choose Download company connection file and Copy employee instructions. Share the file and instructions through your normal company channel.

The connection file contains only your manager’s HTTPS address and the connection format version. It contains no credentials or employee identities. Assignment and first-computer progress stay in the local manager.

For staff changes, use Remove seat or Reassign in People & licenses and review the old computer’s remaining offline deadline. Entra directory changes do not automatically remove local assignments; IT must remove seats in the manager. Use Devices to review active computers and Activity to review the change.

You’re ready when each intended employee has a seat and receives the connection file, installation instructions and your IT contact.

Three steps. No license key to copy.

1. Install PolyPDF.

   Use the Teams-compatible Mac or Windows release supplied by IT. Connect to your company network or VPN if your license service requires it.

2. Open your company profile.

   In PolyPDF licensing, choose Open company profile and select IT’s polypdf-company.json file. You can also enter the company HTTPS address manually.

3. Sign in with your company.

   Choose Sign in with your company. For Microsoft mode, complete sign-in and any MFA in your browser and confirm the computer. For local mode, enter IT’s private invitation in the browser, then contact IT to confirm the matching code and approve this computer. Keep PolyPDF open and return after approval.

Check the company-license status for your organization, assigned user, computer, connection and offline expiry. If no seat is assigned, ask your IT administrator to assign one, then retry. Keep any existing personal key; company sign-in is separate.

Getting started with PolyPDF
1. Install the PolyPDF version supplied by your IT administrator.
2. Open PolyPDF licensing, choose Open company profile, and select the polypdf-company.json file supplied by IT. You can also enter the company HTTPS address.
3. Choose Sign in with your company. For Microsoft mode, complete company sign-in and confirm your computer. For local mode, enter the private invitation from IT and ask IT to confirm the matching code and approve your computer. Return to PolyPDF.
Your administrator must assign your seat. Connect to the company network or VPN if needed. Contact your IT administrator if sign-in or access fails.

You’re ready when PolyPDF shows active company access for you and this computer.

Get back to work.

Employees should contact their IT administrator first. For product help, contact PolyPDF support with the error’s support reference, app and manager versions, and the time it occurred. Do not include passwords, client secrets, enrollment codes or private keys.

Keep the service ready.

Use Service health to check authorization and Activity to review administrative changes. Closing the console does not stop the service. Keep the server available and renew certificates and Microsoft credentials before they expire.

Understand offline access

The manager validates purchased capacity daily. Employee apps check on launch, reconnection and every five minutes while online. Offline access lasts no more than seven days and never outlives the company authorization.

Removing or reassigning a seat prevents the manager from issuing further access to the former holder immediately. Connected computers apply the change by their next check; offline computers retain only their existing entitlement until its displayed deadline. Replacement can therefore create a bounded period of offline overlap.

If access expires, documents and unsaved edits remain available to save or export. New Pro operations are blocked until access is restored.

Your firm controls employee access

Employees use your firm’s Microsoft Entra accounts or locally approved invitations; they do not create PolyPDF accounts. The PolyPDF website account is for the billing owner to purchase seats and enroll the manager. Your administrator controls employee assignments and computers in the company-hosted manager.

Microsoft mode authenticates through Microsoft’s cloud. Local invitation mode keeps employee enrollment and computer approval entirely on your company server. Both modes still validate purchased capacity with PolyPDF daily and have bounded offline access; neither is an air-gapped license system.

What stays with your company

Employee identities, seat assignments, device details and administrative history stay on your company manager. Licensing collects no PDFs, filenames, paths, thumbnails or document activity. Microsoft handles authentication only when you choose Entra mode. PolyPDF receives organization/license identifiers, manager identity and authorization version to validate purchased capacity.