← Downloads

IT deployment guide

Reference for administrators deploying AutoDoc on managed Windows PCs. End users should not fight blocked browser downloads on locked-down devices—deploy this signed MSI through your standard tools, then let users activate Pro licenses inside the app.

Current release: 1.0.0 · AutoDoc_1.0.0_x64_en-US.msi (downloads page, same as in-app updates).

1. Product summary

AutoDoc is a local-first Windows desktop application. It records screen interactions and UI context to build step-by-step guides. Guide content (screenshots, steps, projects) stays on the device unless the user exports files or configures their own shared folder for collaboration (Pro).

Online connectivity is used for license verification (Pro) and optional in-app updates—not for hosting customer documentation on AutoDoc servers.

Public software profile and reviews: Capterra.

2. Installer package

  • Format: WiX MSI only (no separate EXE installer channel).
  • File name pattern: AutoDoc_<version>_x64_en-US.msi (semver in the filename; version changes per release).
  • Current build: version 1.0.0 — AutoDoc_1.0.0_x64_en-US.msi
  • Download: autodocguide.com/downloads — use the MSI linked there, or mirror from https://autodocguide.com/downloads/
  • Update manifest: https://autodocguide.com/downloads/latest.json

3. Publisher and code signing

Shipping builds are signed with Authenticode (EV code signing). Before mass deployment, verify on a sample machine:

  1. Right-click the MSI → Properties → Digital Signatures.
  2. Confirm publisher AutoDoc Guide and a valid timestamped signature chain.

Certificate SHA-1 thumbprint (for allow-listing): FCCD23224601BDAE9974020B76703C7B0A4AEBC4

In-app updates use a separate Tauri updater signature inside latest.json; that is not the same as the MSI Authenticode signature.

4. System requirements

  • OS: Windows 10 or 11, 64-bit (x64).
  • Runtime: Microsoft Edge WebView2 Runtime (Evergreen). Pre-install or let the MSI/bootstrap handle it if your image lacks WebView2.
  • Privileges: Per-machine install under %ProgramFiles%\AutoDoc requires an elevated install (administrator or delegated deployment role).

5. Installation paths

Recommended for enterprises: Microsoft Intune (Win32 app), Configuration Manager (SCCM), or another software catalog using the same MSI.

Default install location: %ProgramFiles%\AutoDoc (user may choose another folder in interactive setup).

Silent install (test in your environment first)

msiexec /i "\\share\AutoDoc_1.0.0_x64_en-US.msi" /qn /norestart

Run from an elevated context. Adjust the path to your staged MSI. Confirm success with msiexec /l*v install.log during pilot if needed. Interactive install remains available from the downloads page for lab machines.

6. Network endpoints

Allow outbound HTTPS from client PCs. autodocguide.com is needed for in-app updates on all tiers; api.lemonsqueezy.com only when users activate or refresh Pro licenses.

Host Purpose
autodocguide.com Update manifest (latest.json) and versioned MSI downloads
api.lemonsqueezy.com Pro license activate / validate (Lemon Squeezy)

Guide screenshots and step text are not uploaded to AutoDoc for storage. Collaboration (Pro) uses paths the customer configures (e.g. OneDrive)—outside AutoDoc hosting.

7. Data on disk

  • Application: %ProgramFiles%\AutoDoc
  • User data: Per-user Windows profile storage (guides, screenshots, and settings). Not synced to AutoDoc servers.
  • License activation (Pro): Bound to the device; profile reset or reinstall may require re-activation.

See the privacy statement for how AutoDoc Guide processes personal data as vendor. Uninstall via Apps & features / MSI product removal; removing user data afterward is optional and irreversible.

8. Updates

Installed AutoDoc checks https://autodocguide.com/downloads/latest.json and may download a newer MSI (passive install mode). Corporate proxies must permit that host, or IT should deploy MSI upgrades on your own schedule and temporarily restrict in-app updates if you pin versions.

Keep older versioned MSIs on your internal mirror if you need rollback; only latest.json defines what the app offers as “current.”

9. Security capabilities (review)

AutoDoc requires permissions typical of desktop capture tools:

  • Global input monitoring (mouse/keyboard) while recording.
  • Screen capture on user actions.
  • UI Automation queries against the active Windows UI tree.
  • Local file read/write under the user profile and install directory.

Endpoint protection may flag new binaries until publisher reputation builds. Allow-listing the signed MSI or install path after pilot is common.

10. After deployment (end users)

  1. Launch AutoDoc from the Start menu or Company Portal.
  2. Free tier works without a license. Pro: open Settings → License Management, enter the organization’s key, then quit and reopen the app (recommended after activation).
  3. Seat limits apply per purchase; stale devices may need a seat released via the customer portal or support.

11. Support contact

Deployment questions: info@autodocguide.com (subject: Corporate rollout).

Include company name, approximate seat count, Windows version, deployment tool (Intune/SCCM/other), and screenshots of any block messages.

Related