Files: Status-based permissions

[matyas_mori]

Hello there,

I’d like to share a (in my opinion) quite revolutionary idea how to completely transform the Files tool and the current role based permission system.

Right now we’re stuck with the default Autodesk system, it definitely has its advantages, but in my opinion this is not how a real CDE should work in 2025. Let’s finally revolutionize how we work in the Files tool.

Instead of complicated folder structures where every folder/subfolder has different role/company/user based permissions, let’s create a clean, non chaotic system:

• One main area with all the project documentation
• Full control via document status
• Every status code would have its own clear permission rules - who can view, download, upload new versions or change the status
• Additional rules could be added through custom attributes

The result? Super intuitive tree/metadata based navigation. Everyone immediately finds what they need and can open exactly the version they’re allowed to see. Example: site workers during construction automatically see only documents with “For Construction” status – no more confusion, no more wrong versions.

As the ultimate bonus and real game changer: everything would be connected through that is set up once at the beginning of the project:

• Every document, sheet, model, asset, location,… would be tagged with the same classification codes.
• Thanks to that, the Files tool would finally become the true backbone of the entire CDE – you click on a classification code and instantly see all related items in one place.
• No more jumping between modules – everything linked through the single classification structure.

This, combined with status-based permissions, would turn ACC into a genuinely connected CDE with a real single point of truth.

I’m convinced this one conceptual shift would be the BIG update that would knock everyone off their chairs.

What do you think? I’d love to hear your opinions and I’m happy to explain the idea in more detail.

Byee

[Mark_Petrucci]

To summarize, you are suggesting:

• Status-based document permissions instead of folder-based permissions
• A shared classification system that connects documents, models, assets, locations, and other project information

I support adding status-based document permissions, but I believe folder-based permissions would still be necessary. Folder permissions can be applied automatically when files are uploaded, without requiring any additional action from the user.

Status-based permissions, on the other hand, would depend on users correctly assigning and maintaining document statuses. That introduces the risk of statuses being missed, avoided, or assigned incorrectly.

A hybrid approach may work best, with folder-based permissions providing the default level of access and status-based permissions adding another layer of control.

I really like the idea of a shared classification system. Connecting documents, models, assets, locations, and other project information through a common classification structure could make information much easier to find and navigate across the platform.