Column Permissions for all non-required columns

Feature Request: Column-level permissions for non-required fields

Summary:
Introduce a configurable permission model that allows administrators to control visibility of all non-required columns within the application. Administrators should be able to hide specific columns from selected user roles or groups so that users only see fields that are relevant to their responsibilities.

Problem Statement:
Today, all users can see many columns that are not relevant to their roles. For example, the “Accounting Calendar” column appears for Estimators/Bidders even though they do not need this information and should not be modifying it. This creates unnecessary screen clutter, increases the chance of confusion or accidental updates to sensitive data, and makes it harder for users to focus on the fields that matter to their workflow.

Proposed Solution:
Add an administration-level “Column Permissions” configuration area where an admin can:

• View a list of all available non-required columns across relevant screens.

• Set visibility for each column by role, group, or permission profile (e.g., “Estimator/Bidder”, “Accounting”, “Admin”).

• Optionally define default visibility rules (e.g., column visible to all unless explicitly restricted).

• Apply changes without requiring code deployments or per-user customization.

At runtime, the UI should:

• Hide columns that are not permitted for the current user’s role/group.

• Ensure hidden columns are also excluded from inline edits, bulk edits, and exports (unless the user has permission).

• Respect these permissions consistently across grids, detail views, and any related reports that display the same columns.

Benefits:

• Reduces visual clutter by limiting screens to only the fields each role actually needs.

• Lowers the risk of accidental or unauthorized edits to sensitive or specialized data (e.g., accounting fields).

• Improves user productivity by simplifying the UI and making it easier to find relevant information.

• Gives administrators more granular control over data exposure without custom development.

• Supports cleaner role-based separation of responsibilities across estimating, bidding, accounting, and other teams.