1,700 Projects, Zero Automation: The Enterprise ACC Problem

TL;DR: A $14B enterprise. 1,700 active ACC🏗️ACCAutodesk's construction management platform.View in glossary projects. Zero way to manage users at scale. We break down the math, the manual pain, and the solution that turns 19 hours of clicking into 45 seconds.

---

The Setup

A $14 billion company. 1,700 active projects in Autodesk Construction Cloud. When a new team member joins, someone has to add them to every relevant project📁ProjectContainer for folders and files within a hub.View in glossary. Manually. One click at a time.

When someone leaves, someone has to remove them. From every project. Manually.

When compliance asks “who has access to what?” — nobody knows.

This is the enterprise ACC problem.

---

The Scale

That last card says “N/A” because a full permission audit is impossible manually. Nobody knows who has access to what across 1,700 projects. There is no export, no report, no dashboard that shows you the full picture.

---

The Manual Workflow

Nearly 19 hours of clicking to add a single person to every project. No breaks, no mistakes, no page-load delays factored in. The real number is worse.

---

What They Actually Needed

None of this exists in the ACC web UI. There is no bulk add. No filtering. No dry-run. No resume. No audit export. Every one of these operations requires a human clicking through a web interface, one project at a time.

---

The RAPS Solution

# Add user to ALL projects -- 1,700 projects, ~45 seconds
raps admin user add "$ACCOUNT" "newhire@company.com" --role project_admin

# Add to only 2024 projects
raps admin user add "$ACCOUNT" "newhire@company.com" \
  --role project_admin --filter "^2024-"

# Remove departing employee from everywhere
raps admin user remove "$ACCOUNT" "departing@company.com"

# Preview before executing
raps admin user add "$ACCOUNT" "newhire@company.com" --dry-run

# Clone permissions from template
raps admin folder set-permissions "$ACCOUNT" \
  --project "$NEW" --clone-from "$TEMPLATE"

# Export for audit
raps admin user list "$ACCOUNT" --format csv > audit.csv

Each of these commands replaces hours of manual work with a single line.

---

Under the Hood

Real-time progress reporting shows completed, failed, and skipped counts as the operation runs. No staring at a spinner wondering if it froze.

---

Before vs. After

---

The ROI Math

$156,000 per year on clicking buttons. That is not an exaggeration — it is arithmetic. Eight people, five hours a week, fifty-two weeks a year.

RAPS turns those five hours into minutes. The math speaks for itself.

---

The Bigger Picture

This is not unique to one company. Any enterprise running more than 100 ACC projects faces the same scaling wall. The admin interface was designed for small teams managing a handful of projects, not enterprises managing thousands.

344 community votes. Six-plus years of waiting. Autodesk’s official response: “Future Consideration.”

RAPS built what Autodesk won’t.

---

Try It

If your organization manages more than a handful of ACC projects, the manual approach does not scale. It never will. The platform was not built for enterprise-scale administration, so you have to build the tooling yourself — or use tooling someone else already built.

Related:

• Admin Commands Reference — Full documentation for raps admin operations
• The ACC Permission Nightmare — Deep dive on permission management gaps
• 4,295 Requests, 60 Delivered — The data behind ACC’s feedback black hole
• ACC Bulk Operations Crisis — Why bulk operations are the most requested category