Bug #2847
Permission Display Name New field and New implementation for user friendly
Added by Piyush Vijay about 2 months ago. Updated 12 days ago.
Description
Permission Display Name New field and New implementation for user friendly
Updated by Shreya Agarwal about 2 months ago
Today I worked on preparing the permission mapping excel sheet by documenting menu and their corresponding permissions keys . the sheet is still in progress and the remaining permissions will be added after completing the pending modules .
Updated by Shreya Agarwal about 2 months ago
completed a comprehensive audit and mapping of the entire application's permission set. I systematically reviewed and documented a total of 217 distinct permissions across all modules, ensuring that every menu item and functional action is correctly linked to its corresponding permission key in the system. This involved meticulously categorizing entries for critical areas like Dashboards, GST, Locations, Partnerships, and Reporting. The final list was compiled into a structured Excel sheet, which now serves as a definitive reference for role-based access control configuration. This thorough exercise ensures that our permission matrix is now fully accurate and aligned with the application's current capabilities.
Updated by Shreya Agarwal about 1 month ago
Backend Work
-Added a new bulk update API endpoint PATCH /api/v1/user/permission/tenant/display-names/bulk that allows updating multiple permission display names in a single request with proper transaction support. Implemented complete validation to prevent updates on default system permissions (is_default = true) and added comprehensive error handling with detailed response messages.
-Created a migration script to add display_name column to all tenant permission tables with automatic backfill from existing permission names. Updated the Permission model and DTOs to include the DisplayName property, and modified the GetAllAsync and GetByIdAsync repository methods to fetch display names from the database.
Frontend Work
-Integrated the display name field across Role Management, User Management, Edit User, and Manage Permissions dialogs, ensuring consistent display of user-friendly permission names throughout the application. Enhanced the permission search functionality in both Role Management and User Management to filter by display name, permission name, and description simultaneously. Updated the TenantPermission interface and API service mappings across permissions API and roles API to properly handle display names from backend responses. Optimized the permission loading to fetch all permissions in a single API call by removing pagination parameters, eliminating multiple API calls that were causing performance issues.
- Added a new ID column to the Excel sheet that corresponds to the permission_id from the database for easy reference and mapping . This Excel sheet serves as the master reference for permission display names, helping to maintain consistency between the frontend UI menu labels and the backend permission system. The sheet includes columns for MENU (display name), PERMISSIONS (permission name), and ID (database permission_id) .
Updated by Yashaditya Singh about 1 month ago
I performed validation of the permission names and corresponding UI page names by cross-verifying them against the Excel sheet to ensure the permissions are correctly mapped and aligned with the respective application pages.
Updated by Shreya Agarwal about 1 month ago
Today worked on updating the total 200 approx Permission Display Names page UI where we mapped and edited display names for all permissions according to the portal requirements, ensuring each permission key has a user-friendly name that matches the organization's language and terminology. Reviewed and updated display names across all permission categories including Admin Push Notifications, Agreement, Dashboard, Stations, Reporting, and Wallets to align with the UI portal standards. Ensured consistency between the permission keys displayed in the UI and their corresponding display names for better user experience. Learned project-based topics and try to analysed some code in project to understand code flow
Updated by Saransh Bakoliya about 1 month ago
Today, I worked on updating and reviewing approximately 200 Permission Display Names across the project, ensuring they match the latest portal requirements and use clear, user-friendly terminology. I checked and updated permission display names across multiple modules, including Admin Push Notifications, Agreements, Dashboard, Stations, Reporting, Wallets, and other permission categories to maintain consistency throughout the application. I verified that each permission key is correctly mapped to its corresponding display name, improving the overall user experience and UI consistency. Additionally, I analyzed the project's codebase to better understand the permission flow and implementation. I also spent time learning project-specific concepts to enhance my understanding of the application's architecture and code flow.
Updated by Shreya Agarwal about 1 month ago
Verified and corrected display names for 250+ permissions across the UI portal by cross-referencing the Excel sheet mapping with actual frontend code implementation. Conducted a thorough search across the entire project to identify all permission usage locations and ensure display names are consistent with their corresponding UI portal pages. Made targeted corrections to Agreement, AWS Settings, and Branding modules where mismatches were found between permission keys and their display labels. Refined the permission display name list to accurately reflect the organization's preferred terminology and aligned them with the actual page headers where permissions are used
also continue learning react and project based code for understanding work flow for assigned tasks.
Updated by Shreya Agarwal 12 days ago
Today updated display names for permissions associated with all newly added pages, ensuring they now reflect the correct organizational terminology across the system. A total of 294 permissions were reviewed. All changes have been applied and updated display names. This helps improve clarity for users and streamlines access management going forward.
also learning react js for enhance knowledge and learn project specific content to understand code flow