IT Approval Information
Details for Autodesk® Revit® · Published by Firm Details LLC · Vendor contact: david@firmdetails.com
This page collects the information IT and security teams usually ask for before approving a Revit add-in. Details is distributed as a digitally signed, per-machine Windows Installer package (MSI), one per supported Revit version. Each section below has a stable link that can be pasted into a software approval request.
Verified publisher and code signing
| Publisher | Firm Details LLC |
|---|---|
| Product names | Details for Revit 2025, Details for Revit 2026, Details for Revit 2027 (one Windows Installer product per Revit year) |
| Installer type | Windows Installer (MSI), perMachine scope, built with the WiX Toolset |
| Signature | Authenticode, SHA-256 digest, using an Extended Validation (EV) code-signing certificate issued by DigiCert to Firm Details LLC. The private key is held in a DigiCert KeyLocker cloud HSM and never leaves it. |
| Timestamp | RFC 3161 timestamp from http://timestamp.digicert.com, so signatures remain valid after the certificate expires |
| What is signed | The MSI package and the Revit add-in DLL inside it (Details<year>.dll). Revit checks the add-in signature at load time, so the add-in loads without Revit's unsigned-add-in security prompt. |
| Website | https://www.firmdetails.com |
How to verify
Right-click the downloaded MSI, choose Properties → Digital Signatures, and confirm the signer is Firm Details LLC with a DigiCert issuer. From PowerShell:
Get-AuthenticodeSignature .\Details-2026.msi | Format-List Status, SignerCertificate, TimeStamperCertificate
Or with the Windows SDK:
signtool verify /pa /v Details-2026.msi
The Windows SmartScreen and UAC prompts show Firm Details LLC as the verified publisher.
Installer SHA-256 hashes
Hashes are recorded when each release is published and are read live from the same release manifest the add-in uses to verify its own updates.
Loading current hashes…
| Revit | File | Version | SHA-256 |
|---|
How to verify a downloaded file
Get-FileHash .\Details-2026.msi -Algorithm SHA256
Or from Command Prompt:
certutil -hashfile Details-2026.msi SHA256
The value should match the row for that Revit year above. Dashboard downloads and in-app updates deliver the same files, so the hashes apply to both. The add-in refuses to install an update whose hash does not match the published value. Beta-channel installers (Details-Beta-<year>.msi) have separate hashes; email david@firmdetails.com if your firm is on the Beta channel.
Required network domains
All traffic is outbound HTTPS on port 443 using TLS 1.2 or later. No inbound ports are required, and no proxy exceptions beyond standard HTTPS are needed.
| Host | Used by | Purpose |
|---|---|---|
details-4f0f1-default-rtdb.firebaseio.com | Add-in, website | License validation, library sync metadata, release manifest for update checks |
firebasestorage.googleapis.com | Add-in, website | Detail thumbnails, in-app update downloads, dashboard backup downloads |
identitytoolkit.googleapis.com | Add-in, website | Firebase Authentication (sign-in) |
securetoken.googleapis.com | Add-in, website | Firebase Authentication token refresh |
us-central1-details-4f0f1.cloudfunctions.net | Add-in, website | Authenticated Cloud Functions: installer listing, download tickets, AI requests, firm administration |
downloads.firmdetails.com | Website | First-party endpoint that streams the signed MSI after a short-lived download ticket is issued |
www.firmdetails.com | Website | Dashboard and Firm Library |
developer.api.autodesk.com | Add-in | Autodesk Platform Services: BIM 360 / ACC / Forma hubs, projects, and publish. Only used when cloud models are linked. |
api.userprofile.autodesk.com | Add-in | Autodesk profile after sign-in (APS) |
accounts.autodesk.com | Browser | Autodesk OAuth sign-in. The callback returns to http://localhost:8080/ on the workstation (local loopback only). |
AI features are requested through the authenticated Cloud Functions host above; Google Gemini / Vertex AI is called server-side inside Google Cloud, so workstations do not need direct access to generativelanguage.googleapis.com.
Revit and Windows compatibility
| Revit | Autodesk Revit 2025, 2026, and 2027 (64-bit). One MSI per Revit year; multiple years install side by side. |
|---|---|
| Operating system | Windows 10 (64-bit) or later, including Windows 11 |
| Runtime | .NET 8.0 Desktop Runtime (x64), which ships with Revit 2025 and later. No separate runtime install is required. |
| Install permissions | Administrator rights are required for installation and updates (per-machine install) |
| Install location (Revit 2025, 2026) | C:\ProgramData\Autodesk\Revit\Addins\<year>\Details\ with manifest C:\ProgramData\Autodesk\Revit\Addins\<year>\Prototype1-<year>.addin |
| Install location (Revit 2027) | C:\Program Files\Autodesk\Revit\Addins\2027\Details\ with manifest C:\Program Files\Autodesk\Revit\Addins\2027\Prototype1-2027.addin, per Autodesk's Revit 2027 add-in security requirements |
| Per-user files | Installation writes nothing to user profiles. At run time the add-in keeps preferences and caches under %LocalAppData%\Prototype1. |
| License server | None. Each user activates with a key that is validated over HTTPS and cached locally; the cached license is used if the network is unavailable. |
Data handling
- Revit models stay on the workstation. The add-in parses models locally and never uploads project files or model geometry.
- What is synced: drafting-view thumbnails and metadata needed to run the library, such as view titles, disciplines, project and sheet names, family names, keynote text, Revit version, source file paths, and model, view, and element identifiers.
- Account data: email, display name, firm membership, role, disciplines, license status, and support communications.
- Autodesk access: users sign in with their own Autodesk account via OAuth. The refresh token is encrypted on the device with Windows DPAPI. The add-in can only reach projects the signed-in user already has permission to view, and an ACC / BIM 360 account admin can revoke the integration at any time.
- AI features: requests are authenticated and processed with Google Vertex AI inside Google Cloud. Firm data is not used to train foundation models.
- Hosting: Google Cloud / Firebase, US-Central region. Data is encrypted in transit (TLS 1.2+) and at rest. Firm data is isolated per firm.
- Deletion: firm administrators can delete synced projects or the entire firm library from the app. Account deletion requests go to david@firmdetails.com.
Full details are in the Privacy Policy and Terms of Service.
Update behavior
- On Revit startup the add-in reads the public release manifest at
details-4f0f1-default-rtdb.firebaseio.com. The check is passive and does not block startup. - If a newer version is published, the user sees an Update Available dialog with release notes and can choose Update Now or Remind Me Later. If the installed version is below the published minimum, the update is marked required.
- When the user accepts, the MSI is downloaded to
%TEMP%\Details-update.msi. The download URL must be onfirebasestorage.googleapis.com, and the file's SHA-256 is checked against the manifest before anything runs. A mismatch deletes the file and aborts. - A helper script waits until every
Revit.exeprocess has exited, then runsmsiexec /i "%TEMP%\Details-update.msi" /passive /norestartwith a verbose log at%TEMP%\Details-update.log. - The MSI uses Windows Installer MajorUpgrade, so installing a newer version removes the previous version for the same Revit year. No manual uninstall is needed.
Managed environments: nothing installs without the user accepting the prompt, and the update still needs installer privileges on the machine. Firms that control software distribution can deploy each new MSI through their existing tool instead; the in-app prompt disappears once the installed version matches the published version.
Deployment
Interactive (single machine)
- Sign in to the Details dashboard and download the MSI for the Revit year in use (for example
Details-2026.msi). - Close every running Revit session.
- Run the MSI and follow the prompts.
- Start Revit. The Details tab appears on the ribbon.
Silent / unattended
msiexec /i "Details-2026.msi" /quiet /norestart
With logging:
msiexec /i "Details-2026.msi" /quiet /norestart /log "%TEMP%\Details-2026-install.log"
SCCM, Intune, GPO
Deploy as a standard Windows Installer package with per-machine scope. No transforms, custom properties, or prerequisites are needed. Detection can use the product code or the installed file Details<year>.dll in the install folder listed under compatibility.
Multiple Revit versions
Install one MSI per Revit year. Each year has its own UpgradeCode and installs side by side:
msiexec /i "Details-2025.msi" /quiet /norestart
msiexec /i "Details-2026.msi" /quiet /norestart
msiexec /i "Details-2027.msi" /quiet /norestart
BIM 360 / ACC / Forma
Linking cloud-hosted models requires an ACC / BIM 360 account administrator to add Details as a Custom Integration once per account. Steps and the Details APS Client ID are in the Help & Documentation page and in the dashboard's IT Deployment Guide.
Uninstallation
Interactive
Windows Settings → Apps → Installed apps, find Details for Revit 20xx, and choose Uninstall. This removes the program files and the Revit add-in manifest.
Silent
msiexec /x "Details-2026.msi" /quiet /norestart
Or by UpgradeCode, which stays constant across versions for each Revit year:
| Revit year | UpgradeCode |
|---|---|
| 2025 | {FF416D93-3E42-494C-91E8-4C3B7E2DF976} |
| 2026 | {428C8B10-08AD-465F-9BDF-00DD90E87576} |
| 2027 | {485FF1CA-2C0E-472D-94F0-B0963F493BCC} |
Local data
Uninstalling leaves per-user application data under %LocalAppData%\Prototype1 (preferences, caches, and an encrypted Autodesk refresh token). Delete that folder to remove all remaining local data.
Contact
Questions from IT or security reviewers: david@firmdetails.com. Include your Revit version and any policy requirements so we can respond with the right documentation.