Send a version to a few people first. Then add more.
What this is
A version leaves the workspace and lands with a person — on the Revit ribbon, in AutoCAD, or as an ACC app in the browser.
Why
You want the same version in a few hands, not four ZIPs. Creators pick the version and the people. Viewers run it.
What lands where
| Host | What they get |
|---|---|
| Revit | A compiled desktop add-in on the ribbon (Revit 2020–2027) |
| AutoCAD | A compiled desktop add-in |
| ACC | A hosted app in the browser. Conduit handles hosting and sign-in. |
A Viewer does not generate. Desktop add-ins can still need IT to allow the runner.
First rollout
- Generate a version and test it on a non-production model or drawing.
- Open Versions.
- Deploy that version to yourself and one or two people.
- If the behavior is wrong, iterate for 20 credits and deploy the new version to the same people.
- Add more people when you would have emailed a ZIP.
Do not start with the whole office.
Change who has it
Open Versions. Deploy the same version to more people or leave someone off. Creators only.
Use an older version
Open Versions. Every generate is its own version. To rewind, deploy that older version.
Credits are not spent on deploy. See Seats, credits, and billing.