Documentation
Installation & activation
Choose the right launcher, start your local workspace, and activate your licence—even when your work computer cannot reach the licence service.
All documentation01 / Prepare
Before you start
Get the current approved stable package from Download. No account or credit card is required. Purchased-release recovery remains available in Account → Downloads. Check the supplied release information, system requirements and checksum before opening the package.
Choose the separate Windows x64, macOS Apple Silicon arm64 or Linux x64 ZIP listed for the approved public release. Each package contains only its selected platform runtime. Your package’s release-specific instructions take precedence over this general guide.
- Extract the complete ZIP into a new, ordinary folder on a fixed local drive. Do not run from inside the ZIP or extract over an older installation.
- Keep the entire extracted tree together. Use a writable folder outside OneDrive, iCloud Drive, Dropbox, network/NAS shares, removable drives and shared VM folders. Avoid linked paths.
- On Mac, also avoid Desktop and Documents, which may be synchronized by iCloud even when their paths look local. Use a dedicated folder in your home directory outside those locations.
- On Linux, use a writable dedicated folder in your home directory on a fixed local disk. The supported filesystem families are ext, XFS, Btrfs and F2FS; a writable, non-removable backing block device must also be verifiable. Locations under
/mnt,/mediaand/run/mediaare excluded by path policy. Overlay/container and memory-backed filesystems such as tmpfs are unsupported for the authoritative database. - Check that your organisation permits the package and chosen entry. The supplied launchers do not require Node.js, npm or package installation at startup.
Already using PM Control Workbench? Follow Updating without losing your work before opening an existing workspace with new software.
02 / Start
Choose your launcher
Start with the supplied entry for your computer. These entries use their bundled Python runtime; you do not need to install Python separately.
| Computer | Entry at the extracted root | How to start |
|---|---|---|
| Windows x64 | Start_PM_Control_Workbench.exe | Double-click the EXE. Keep its runtime console open. |
| Mac, Apple Silicon (arm64) | Start_PM_Control_Workbench.command | Double-click the command file, or use the Terminal command below. |
| Linux x86-64 | Start_PM_Control_Workbench.sh | Open a terminal in the extracted folder and use the command below. |
Mac Terminal
./Start_PM_Control_Workbench.command --port 8801Linux terminal
./Start_PM_Control_Workbench.sh --port 8801Open the local browser address printed by the launcher, for example http://127.0.0.1:8801/. It points to the Workbench on your computer. Use a browser supported by your package. Add --no-browser if you prefer to open the address yourself.
When your company permits Python instead
Where your organisation explicitly approves this entry, a supported package can run through Start_PM_Control_Workbench.py using an IT-approved, compatible 64-bit Python 3.11 or newer. The active Python installation must already include the approved cryptography component used to verify licences. Python being present alone is not sufficient.
Close every Workbench runtime first. In a terminal opened in the extracted folder, use the command for your approved Python installation:
Windows Command Prompt
python -B -I -S Start_PM_Control_Workbench.py --port 8801Mac or Linux terminal
python3 -B -I -S Start_PM_Control_Workbench.py --port 8801Have IT confirm that python or python3 selects the approved interpreter. This is an explicit alternative, with no automatic fallback. See IT requirements if it is unavailable or blocked.
Closing a browser tab does not stop the Workbench. Wait for Saved and zero pending edits, press Ctrl+C in the runtime console, and wait for it to exit before switching entries or moving the folder.
03 / Activate
Start the trial or activate a purchase
The first eligible launch starts your 30-day trial automatically. No account, browser approval or licensing-service connection is needed. Reinstalling or deleting ordinary settings does not restart the trial.
When purchasing is available, choose Buy PMCW after the trial ends. Create or sign in to your purchaser account and complete checkout. PMCW checks for completion and installs the verified licence automatically; no code copying or manual Check step is needed.
Already purchased? Use this route when the Workbench computer can reach the licence service. You need an eligible licence or operator grant; signing in alone does not grant use.
- In the application, open Settings → About → License → Activate an existing purchase.
- Follow the opened browser page to the account website. Sign in as the licence owner or authorised assignee.
- Review the device, select an eligible licence if prompted, and choose Approve this device.
- PMCW finishes activation automatically. Confirm the licence status allows editing on this device and version.
If the browser cannot open the account site, or the application cannot contact the service, use the file-exchange route below from another permitted computer.
If opening Account → License yourself, expand Manage activation to see the activation controls.
Open Account → License03 / Alternative activation
Activate with a .lic file
Your work computer can remain offline, or have the licence website restricted by IT. A second, permitted computer with internet access handles the request and response. Use your organisation’s approved method to transfer the files.
- Work computer: open Settings → About → License → Create offline request. Save the generated request file.
- Connected computer: sign in at pmcontrolworkbench.com → Account → License using the eligible account.
- Expand Manage activation if needed. Under Process an activation request file, upload the request and select Create signed response. Download the signed
.licfile. - Original work computer: return the response, select Import .lic response in the License card, and choose the downloaded file.
- Confirm the licence is verified and permits editing. Make a small edit, confirm Saved, stop normally and restart to check it remains saved.
Do not copy another computer’s activation or transfer private keys. Creating a request does not activate the device. Fresh activation still requires a connected computer to obtain a signed response. If the licence service itself is unavailable, wait for it to return or contact support; file exchange cannot issue a new licence during a service-wide outage.
If no permitted connected computer or approved transfer method is available, ask IT or support to arrange activation.
04 / Keep working
Check your setup
- Check that the expected workspace and licence status appear. An unexpectedly empty workspace is a reason to stop and confirm its location.
- Create a small test project or edit, wait for Saved and zero pending edits, stop the runtime, then restart using the same entry. Confirm the edit survived.
- Create a verified backup and check it in Backup Explorer. Keep backups in an approved location separate from the live workspace.
After activation, including offline use
The €149 one-time licence grants permanent use of the purchased eligible release. PM Control Workbench may make corrective or maintenance builds eligible where appropriate. Future commercial releases are not automatically included unless explicitly stated; semantic version numbers do not define entitlement. The licence is verified locally without a heartbeat or recurring refresh. No renewal is required. A valid installed licence remains usable during service outages or retirement; initial issuance and replacement-device activation need the service.
The full 30-day trial needs no card and never converts automatically. After expiry, editing pauses; reading, search, export, backup and recovery remain available. Future commercial releases may require a new purchase; future development, upgrades and discounts are not promised. Historical issued licences retain their signed terms.
Activation is device-bound: moving software on the same computer and activating a different computer are different operations. Keep your licence backup and protected device identity. A saved .lic file can restore entitlement on the original identity; it cannot activate a different device or recreate lost private keys. Use the authenticated activation path for available replacement-device slots.
Know where your workspace lives
Follow the storage location documented for your package. A universal portable keeps its workspace under user_db inside the extracted folder. The Windows package uses %LOCALAPPDATA%\PM Control Workbench\user_db; moving its software folder does not move that workspace. Never copy a live SQLite file to transfer your work. Use the supported verified backup and restore process.
For the offline manual, open Settings → About → Open User Manual or Help → User Manual. The supplied RELEASE_INFORMATION.html contains package-specific launch information.
For your IT team & troubleshooting
What IT needs to approve
- Package and entry: the supplied release, host architecture, publisher trust and selected launcher. Follow its release-specific signing and policy instructions.
- Python alternative: an approved compatible 64-bit Python 3.11+ and its already-installed
cryptographyEd25519 provider in the active interpreter’s environment. It selects Python SQLite rather than the packaged native persistence DLL; the verification component has its own dependencies that IT must permit. Missing verification support leaves the runtime read-only. - Local access: the approved writable data location and a supported browser connecting to
127.0.0.1on the selected local port, such as8801. The browser and runtime run on the same computer. - Online activation: outbound HTTPS to
https://pmcontrolworkbench.com(port 443), including/api/v1/licensing/, from the runtime. The account browser also needs the site’s managed sign-in service permitted. IT can review its required identity domains through support. Project records and attachments are not sent to the licence service. - Offline activation: a permitted connected account browser and approved request/response transfer. The work computer itself needs no licence-service connection for file exchange.
The standard supplied entry needs no administrator launch. Organisation policy still governs execution, Python and its dependencies, local ports and file transfers. Do not disable SmartScreen, Gatekeeper, AppLocker, WDAC or endpoint protection to run the application.
Find the next step
- Linux reports PORTABLE_DATA_ROOT_INVALID
- Read the displayed path, filesystem and storage check. Startup stops before opening project data. A prohibited-prefix error describes a path rule, not a detected removable device. For overlay/container, network/shared or removable storage, stop all Workbench processes and move the complete extracted folder to a supported fixed local disk. For a non-writable directory, choose one you can write to. If the backing device cannot be verified, ask IT or support to check the location. A supported filesystem alone is insufficient, and changing launch commands does not bypass the storage policy.
- Windows blocks the EXE or native component
- Stop the attempt. Ask IT whether the supplied package’s explicit Python entry and its prerequisites are approved. If neither entry is permitted, contact IT/support.
- Python is missing, has the wrong architecture, or cannot verify licences
- Have IT provision or select the approved compatible interpreter and verification provider. Do not install packages during launch or alter licence files. A read-only state does not mean project data was deleted.
- Mac reports that the launcher cannot be opened
- Have IT confirm the supplied package’s trust and policy status. Follow its approved signing/Gatekeeper instructions. Changing launch commands does not establish trust.
- Mac or Linux reports permission denied after a folder transfer
- For execute-permission loss only, the supplied launchers support
sh Start_PM_Control_Workbench.command --port 8801on Mac orsh Start_PM_Control_Workbench.sh --port 8801on Linux. This restores required user-execute bits; it does not override security policy. For a missing runtime or unsupported architecture, obtain the correct complete package. - The browser does not open, or the port is already in use
- Use the local address printed by the runtime. Close any previous Workbench runtime before restarting. If another application owns the port, ask IT for an available approved port and pass it with
--port. - The licence website is restricted or the work computer is offline
- Follow Activate with a .lic file using another permitted computer for initial or replacement-device activation. An outage prevents issuing a fresh response; a valid installed licence for the purchased eligible release continues working offline without renewal or recurring validation.
- The request or .lic response is rejected
- Confirm the correct account, eligible licence, device allowance, original requesting computer and unmodified file. For expired requests, create a new one on that computer. The 30-day trial uses protected time; clock rollback during a trial may require trusted online time verification. A valid permanent licence needs no recurring online refresh. Contact support with the redacted error if it persists.
- The workspace is locked or unexpectedly empty
- Stop and confirm no other runtime owns the workspace and that you opened the right package/data location. Do not delete locks, recovery files or the old workspace. Consult the package instructions and support before importing anything.
Contact support
Email support@pmcontrolworkbench.com with your software version, operating system/architecture, selected entry and redacted error. Review diagnostics before sharing. Do not send passwords, private keys, licence file contents or your workspace database.