Revit Cloud Model Initialization Tool
Stand up new Autodesk Construction Cloud projects from a Revit template in minutes — worksharing enabled, links repaired, permissions stamped, ready for the team.
What it does
One-click cloud init
Pick a template, name the project, hit Initialize. The tool creates the ACC project, folder scaffold, role permissions, and uploads the seed model with worksharing enabled.
Automated link repair
Walks the link graph, re-resolves CAD/RVT/PDF references against the new cloud paths, and writes a diff log of every relink it performed.
Migrate from anywhere
File-server → cloud, BIM 360 → ACC, and cloud → cloud all share one workflow. Configure source, configure target, run.
Audit log on every run
Every initialization writes a signed JSON audit record to your firm's project folder — no more 'who set this up and when' tickets.
Permission templates
Stamp standard role permissions (Architect, MEP, Owner, Subs) from a YAML template the BIM lead controls. No more click-fests in the ACC UI.
Headless mode
Drive the tool from a CLI for unattended scripted setups across dozens of jobs. Same engine as the ribbon UI.
How it works
Five steps. The first four are the tool's job.
-
1
Authenticate
Sign in to ACC with your Autodesk credentials. Tokens are stored in the Windows Credential Manager — no plaintext on disk.
-
2
Configure
Choose source (template, file-server folder, or existing cloud project) and target (Hub → Project → Folder). Set permission template and naming pattern.
-
3
Initialize
The tool creates the ACC project, uploads the seed model, enables worksharing, repairs links, and stamps permissions in a single transactional run.
-
4
Verify
Review the audit log, link diff, and permissions report. Anything that didn't apply cleanly is flagged with the exact ACC error code.
-
5
Hand off
Send the project URL to the team. They open it like any other ACC project — no special client, no DSQ runtime required.
Compatibility
What runs, what's required, what's tested.
Security & licensing
The bits IT wants to see before they sign off.
Offline license validation
Licenses are JSON files signed with an Ed25519 private key held in Azure Key Vault. The add-in validates against an embedded public key with no network call.
No telemetry, no analytics
We do not collect usage data from inside the product. No phone-home, no kill-switch, no mandatory cloud check-in.
Per-firm, per-Revit-year
One license file covers every seat at the company for one Revit year. Upgrade releases ship as separate licenses to keep the API surface bounded.
Stripe-handled checkout
Payments go through Stripe Checkout — we never see your card. Receipts and tax invoices are issued automatically.
Signed installers, SAS-gated downloads
MSI installers are Authenticode-signed. Download URLs are short-lived Azure Blob SAS tokens scoped to your active license.
Data residency
We do not store your model data. The tool talks directly from your machine to Autodesk's APS endpoints over HTTPS.
Pricing
One price. One Revit year. Every seat at your firm.
Per-firm license
RecommendedLifetime, locked to one Revit year. Unlimited seats at the firm.
- Unlimited seats at one firm (single Revit year)
- All v1.x updates for that Revit year — free
- Email support, 1 business-day response
- Signed audit log for IT review
- 30-day money-back
Trial license
Same binary, 14 days, no card required.
- Full functionality, no watermark
- License file expires after 14 days
- Issued from a firm email address
FAQ
What does 'per-firm lifetime' actually cover?
One purchase covers every seat at your company (same legal entity, same payroll) for one Revit version year. There is no seat count to manage and no annual renewal.
How are upgrades handled?
When you adopt a new Revit version, you purchase the license for that version. Existing-firm customers get a 40% upgrade discount on adjacent years (e.g. 2025 → 2026).
Does this require Autodesk Platform Services credentials we don't already have?
No. The tool uses the same ACC entitlement your team already has (Docs + Build). We do not provision anything on the Autodesk side.
What's the support SLA?
Email support with a 1-business-day response for licensed customers. Critical bugs (data loss, license validation failures) are triaged same-day.
Can I deploy this via Intune / GPO?
Yes. Ships as a standard signed MSI plus a .addin manifest. Drop the license file in %ProgramData%\Autodesk\Revit\Addins or push via your existing channel.
What happens if my company changes name or merges?
Email us — license re-issuance for genuine corporate changes is free. We just want a paper trail so resale through M&A doesn't become an unintended channel.