Summary
This guide explains how the Acelab Revit add-in is installed and updated, so IT administrators can configure deployment policies that work with their firm's security requirements. It covers the initial install process, how automatic updates work, and what permissions are needed at each stage.
Before You Begin
Download the Acelab Revit add-in here
The Acelab Revit add-in is compatible with Revit versions: 2022, 2023, 2024, 2025, 2026)
Familiarity with your firm's software deployment policies (e.g., centralized management tools, installer allowlists, user permission levels)
Access to standard Windows admin or user accounts depending on your deployment model
How Installation and Updates Work
The Acelab Revit add-in uses a two-part approach to balance IT control with minimal disruption to end users.
Initial install uses a standard MSI installer. Subsequent updates use a lightweight EXE-based updater that runs at the user level.
Think of it like setting up a mailbox (MSI install) versus receiving mail (EXE updates). IT handles the one-time setup, and routine deliveries happen without needing to involve IT again.
Install Location
The add-in installs to the user's AppData folder, which is a non-admin directory. This follows Autodesk's guidance for Revit add-in placement and does not require elevated permissions for the install target.
Initial Installation (MSI)
The first install uses an MSI package, which gives IT teams full control over deployment.
Download the MSI installer from acelabusa.com/revit.
Deploy the MSI using your preferred method — manually, via Group Policy, SCCM, Intune, or another management tool.
The installer places the add-in files in the user's AppData directory.
After installation, an Acelab tab appears in the Revit ribbon the next time a user opens Revit.
For centralized deployment: IT admins can deploy the MSI once per machine or per user profile, depending on their management approach. No additional configuration is needed after installation.
Automatic Updates (EXE)
After the initial install, the add-in checks for updates and applies them using an EXE-based updater rather than MSI.
This is the key distinction for IT planning: the updater runs at the standard user level and does not require admin permissions. This means end users can receive updates without submitting IT tickets or waiting for admin approval.
What this means for your policies:
The EXE updater does not trigger UAC (User Account Control) prompts
No elevated permissions are requested during updates
Updates apply only to the current user's add-in installation
The update process does not modify system-level directories or registry keys outside the user's profile
What IT Admins Should Know
If your firm uses application allowlists or endpoint protection: You may need to add the Acelab updater executable to your allowlist. The updater runs from within the user's AppData directory. Contact Acelab support for the specific file paths and signatures if needed for your allowlist configuration.
If your firm uses centralized software management (SCCM, Intune, etc.): You can continue using the MSI for the initial rollout. Once installed, end users will receive updates independently through the EXE updater. If you prefer to manage updates centrally as well, you can disable automatic updates and deploy new MSI versions on your own schedule — contact Acelab support for details on this configuration.
If your firm restricts EXE execution in user directories: Some security policies block executables running from AppData. If this applies to your environment, you will need to create an exception for the Acelab updater, or manage updates centrally using the MSI. Reach out to Acelab support for guidance specific to your setup.
Outcome
After deployment, end users will see the Acelab tab in their Revit ribbon and can sign in with their Acelab credentials. Updates will apply automatically without requiring admin intervention, unless your firm's policies require a different approach.