Allow Project Admins to Configure Role Based Default Views for Data Grids (Issues, Forms, Reviews, Submittals, RFIs)

[RAKESH_R_PATIL]

Allow Project Admins to Configure Role‑Based Default Views for Data Grids (Issues, Forms, Reviews, Submittals, RFIs)

Problem Statement

In Autodesk Construction Cloud (ACC), data grid views (e.g., column visibility, column order, filters, sorting) in modules such as Issues, Forms, Reviews, Submittals, and RFIs are currently stored locally at the user/browser level (cache‑based).

As a result:

• Each user must manually configure their preferred view on their own screen.
• If the user:

• clears browser cache,
• logs in from another system/browser,
• uses an incognito/private session, or
• switches devices, the data grid reverts to the system default view.

This leads to inconsistent user experience, repetitive configuration work, and operational inefficiencies—especially on large, multi‑user projects.

Current Limitation

• Data grid configurations are:

• User‑specific
• Browser/cache‑dependent
• Not centrally controllable by Project Admins

• There is no capability for a Project Admin to:

• Define a standard default view for a project.
• Assign different defaults based on user roles (e.g., QA/QC, Consultant, Contractor).
• Ensure consistent visibility of critical columns (Status, Ball‑in‑Court, Due Date, Location, etc.).

Why This Is a Problem (Real Project Impact)

On large projects (e.g., high‑rise, infrastructure, multi‑tower developments):

• Teams rely heavily on grid‑based workflows to:

• Track responsibility (“Ball in Court”)
• Monitor due dates and overdue items
• Filter by location, package, or discipline

Without centrally managed default views:

• New users are confused about what information matters most.
• Different stakeholders see different data for the same module.
• Training effort increases because users must be taught how to configure views, not just how to use the workflow.
• Administrators cannot enforce process consistency.
• Time is wasted repeatedly re‑configuring grids after cache loss.

Proposed Enhancement (Solution)

Role‑Based Default Data Grid Views Managed by Project Admin

Introduce a capability where:

• Project Admins can:

• Configure default data grid views per module (Issues, Forms, Reviews, Submittals, RFIs).
• Assign these default views role‑wise.
• Modify and update them centrally.

Example Capability

Role	Default Grid View
Project Manager	Status, Ball in Court, Due Date, Priority
QA/QC	Status, Location, Issue Type, Root Cause
Consultant	Title, Discipline, Due Date, Reviewer
Contractor	Status, Assignee, Location, Action Required

Expected Behaviour (Recommended UX)

• Each module provides:

• “Set as default view (Admin)” option (role‑aware)

• When a user logs in:

• The system loads the role‑assigned default view
• This works across devices and browsers

• Users may still:

• Temporarily customize their view
• Reset back to Admin‑defined default at any time

Applicable Modules

This enhancement would be extremely valuable for:

• Issues
• Forms
• Reviews
• Submittals
• RFIs

(All modules that primarily operate via data grid / list views)