Currently, permissions in Autodesk ACC apply at the overall issue level – meaning that all users with issue permissions can see and create all issue types that exist in the project.
This creates challenges, particularly on construction sites:
Contractors and field workers are often presented with a long list of issue types, many of which are irrelevant to their role.
This increases confusion, leads to frequent mistakes when selecting issue types, and results in poor data quality for later reporting.
Certain workflows, like using Tasks for field assignments, lose their impact because everyone who can create issues can also create Tasks, even if that is not intended for their role.
Proposal
Introduce granular issue type permissions, so that access can be managed at a much deeper level:
Issue-Type Level Control: Allow permissions to be set per issue type, for individuals, companies, or roles.
Create vs. Receive Permissions: Add a general setting where some users can only receive and respond to issues, but not create new ones.
Benefits
Simplified User Experience: Users only see the issue types relevant to their role, making the interface less overwhelming.
Fewer Mistakes: Less risk of choosing the wrong issue type, improving overall data quality.
Better Reporting: Cleaner data leads to more reliable analytics and KPIs later in the project.
Controlled Workflows: Maintains the intended purpose of specific issue types (e.g., Tasks stay meaningful as a top-down assignment tool rather than being misused by everyone).
Wider Adoption of Issues: With a clearer, role-specific experience, teams are more likely to use issues consistently.
