Autodesk Construction Cloud project setup reaches far beyond creating a job name. The launch team must choose the right hub and template, decide what belongs in the common data environment, establish folder and naming controls, configure field workflows, and prove that project members can complete their work without excessive access.
Autodesk's current help uses Hub Admin for parts of the administration experience and describes Forma Data Management as formerly Autodesk Docs while still identifying it as the common data environment included with Autodesk Construction Cloud offerings. This guide uses the familiar ACC, Docs, and Build terms but treats the labels shown in the current tenant as authoritative.
Project templates can accelerate repeatable work, but Autodesk notes that only supported products, tools, settings, and items are included. A dependable rollout therefore uses an explicit baseline register and a new-project pilot rather than assuming that every configuration from an older project will appear in the template.
Key decisions at a glance
- Choose a blank template, an approved existing project, or an Autodesk sample only after documenting which supported settings should become the reusable baseline.
- Publish and retire templates through named hub governance so project creators can distinguish an approved configuration from an experiment or outdated copy.
- Create the project with the correct hub, number, type, time zone, dates, and template because those choices establish context for downstream field and reporting workflows.
- Design Docs folder permissions and naming standards together, accounting for inherited access, alternative grants through users, roles, and companies, and noncompliant-file handling.
- Pilot Build issue and form settings with representative office and field roles before the wider project invitation and document every project-only exception.
Govern What the ACC Project Template Is Allowed to Standardize
Autodesk permits project templates to be created blank, from an existing project, and, where available, from a sample template saved to the hub. Begin by listing the recurring construction controls the organization wants to reuse: supported folder structures, issue settings, form templates, report templates, product configuration, and approved project-member patterns.
The existing-project route is useful only when the source project is clean and the administrator is a member of it. Autodesk warns that only project items supported by the template system are copied, so compare the resulting template configuration with the baseline register before treating it as a complete duplicate of the job.
Use publishing status as an operational gate. A published template should have an owner, intended project types, version or effective date, last validation project, and retirement decision. Hub administrators can also restrict project administrators from creating projects or templates, which helps keep unauthorized copies out of the project-creation flow.
- Record each supported Docs, Build, Cost, Takeoff, and Design Collaboration control the template is expected to include.
- Identify settings and records that require manual completion after project creation instead of implying that the template carries everything.
- Publish only approved templates and archive superseded versions after confirming no active creation process still depends on them.
- Create a controlled test project from the candidate template and retain screenshots or exports that prove the expected configuration.
Create the Project With Accurate Administrative Context
The project-creation record should come from the signed job and the organization's project registry. Confirm the hub, project name and number, project type, address, time zone, start and end dates, value, and selected template before clicking Create; a similar project name is not enough to prove the correct accounting or delivery context.
Autodesk notes that the browser's time zone is used as the default and that not every tool uses the project time zone. Record which date-sensitive workflows the team will validate, including reports, notifications, schedule activity, issue due dates, and integrations, rather than assuming one project setting controls every timestamp.
After creation, the creator becomes the first project administrator. That person should add a second approved administrator, confirm the project identity, enable only purchased and required products, and complete the manual configuration items in the baseline register before inviting the wider team.
- Reconcile the project number, name, hub, delivery type, address, time zone, dates, and value with the approved job record.
- Select the intended published template and record its owner and validation date in the launch checklist.
- Separate product activation from member invitations so incomplete project settings are not exposed to the field team.
- Verify administrator coverage and escalation contacts before the original project creator leaves the setup window.
Engineer Docs Folder Access and Naming Behavior Together
Autodesk Docs folder permissions can be assigned to individual members, roles, companies, or Everyone. Subfolders inherit the parent's permission, and a changed subfolder permission must match or exceed the parent. Build the folder tree around real information exchanges and separate confidential commercial, design, owner, and trade-package areas before granting access.
Effective access can come from more than one path. Autodesk explains that removing a user, role, or company permission does not remove access retained through another grant or through project-administrator status. A permission report and a test account for each representative role are more reliable than inspecting one row in the folder panel.
A Docs naming standard uses ordered attributes to enforce predictable file names and can be applied to selected folders. Apply and test the rule before those folders fill with production files; when required values are missing, the file validator and optional holding-area behavior can affect whether a file appears in its intended folder.
- Define each top-level folder's owner, audience, allowed file actions, retention purpose, and expected downstream consumers.
- Assign permissions through stable roles or companies where practical, then document necessary individual exceptions and their expiration dates.
- Test inheritance and alternative access paths with users who represent internal, design, owner, and subcontractor perspectives.
- Apply naming standards and required attributes early, then verify upload, validation, holding-area, move, and correction behavior.
Pilot Build Issue and Form Workflows Before Mobilization
Autodesk Build issue settings include categories and types, custom fields, permissions, root causes, templates, and statuses. Configure only the fields that support a defined response or report, and keep type names distinct enough that a field user can select the right one without consulting a long reference guide.
Form templates should mirror the inspection, safety, quality, or turnover decision they support. Assign a business owner, test response types and section responsibilities, confirm references to the correct Docs material, and verify that the resulting form can be completed on the devices and connectivity conditions used at the site.
Run the pilot with a project administrator, document controller, superintendent, project engineer, and at least one external collaborator. Record failures as template defects, project-specific exceptions, permission defects, device or network issues, or training needs so the correct owner fixes the root cause before mobilization.
- Create a small representative set of issue types, statuses, custom fields, permissions, root causes, and templates.
- Build form templates around an accountable field decision and link only current supporting material.
- Test office and mobile experiences with the roles, devices, and site conditions that will be present during production.
- Complete a post-pilot review and update the reusable template only with approved changes that belong on future projects.
Vendor documentation and ALLMSP resources
- Autodesk: Project Templates
- Autodesk: Create Project Templates
- Autodesk: Supported Products and Tools in Project Templates
- Autodesk: Create and Manage Projects
- Autodesk: Manage Folder Permissions
- Autodesk: Project Member Folder Permission Levels
- Autodesk: File Naming Standards
- Autodesk Build: Issues Settings
- Autodesk Build: Create a Form Template
- Autodesk: Current Docs and Forma Data Management Naming
- ALLMSP Software Support
- ALLMSP Cybersecurity
- ALLMSP Construction and Contracting
- ALLMSP Autodesk Construction Cloud Support
- Contact ALLMSP
Frequently Asked Questions
What can an Autodesk Construction Cloud project template standardize?
Project templates can carry supported configuration for Autodesk Docs, Build, Cost Management, Takeoff, and Design Collaboration. Autodesk publishes a current supported-tools list, so verify each required item and keep manual setup tasks in the launch checklist.
Should an ACC template be created blank or from an existing project?
Use a blank template when you want a deliberately designed baseline. Use an existing project only when its configuration has been reviewed and the administrator is a member; Autodesk copies only supported template items, not every piece of project data.
What does publishing an Autodesk project template do?
Publishing makes an approved template available to project creators in the hub. Treat publication as a governance decision with an owner, intended use, validation evidence, and a process for unpublishing or archiving outdated versions.
Can hub administrators restrict who creates ACC projects and templates?
Yes. Autodesk documents a hub-level setting that can prevent project administrators from creating projects and templates. Use it when the organization needs a controlled project-intake and template-approval process.
Does an Autodesk project template copy every setting from the source project?
No. Autodesk states that only supported tools, features, settings, and project items are copied into a template. Build a test project and compare it with the organization's baseline register before rollout.
How do Autodesk Docs folder permissions inherit?
Subfolders inherit the parent folder's permission. If a subfolder is changed, Autodesk requires its permission to match or be greater than the parent's level, so a sensitive area may need a separate parent structure rather than a lower child permission.
Why can a member retain Docs access after one permission is removed?
The same person may still receive access through another user grant, a role, a company, or project-administrator status. Autodesk's permission guidance explicitly distinguishes the access path removed from the paths that remain.
When should a Docs naming standard be applied?
Apply and test it before production folders contain files. Naming standards and required attributes affect validation, and noncompliant files may enter a holding area or fail to display in the intended folder depending on configuration and action.
Which Autodesk Build issue settings belong in a rollout pilot?
Test the approved categories, types, custom fields, permissions, root causes, templates, and statuses with actual field and office roles. Confirm assignment, visibility, mobile entry, reporting, and closeout behavior.
How can ALLMSP help standardize Autodesk Construction Cloud projects?
ALLMSP can assess existing templates, document the supported baseline, review Docs folder and naming controls, configure pilot plans, test Build workflows, and create administrator and field handoffs that fit the contractor's operations.
