Bug #3017
Add Reporting Catalog Categories View Permission
Description
Implement a new permission for viewing catalog categories in the Reporting module.
Permission:
reporting.catalog.categories.view
Changes:
Add the reporting.catalog.categories.view permission to all existing tenant schemas.
Assign the permission to user_id = 1 and role_id = 1.
Assign it to company_admin and tenant_admin roles when present.
Do not grant this permission to other roles by default.
Update the Catalog Categories API to use the new permission instead of the broader ViewSupport permission.
API:
GET /categories
Update the permission attribute to:
[RequirePermission(SystemPermissions.ViewReportingCatalogCategories)]
Migration:
Create:
V0140_add_catalog_categories_report_permission.sql
The migration should safely create the permission only when it does not already exist and avoid duplicate user/role permission assignments.
Updated by Yashaditya Singh about 2 months ago
I worked on refining the permission-based access control for reporting and partnership features. Added dedicated reporting.catalog.categories.view and reporting.catalog.categories.manage permissions for the Catalog Categories APIs, updated the backend controller and frontend sidebar/route permissions accordingly, and created the related database migration. Also introduced the dedicated partnership.partners.payout_process.view permission for both Partner Payout Process APIs, updated SystemPermissions, sidebar access, and the Partner Payout Process route to use the new permission instead of the broader ViewPartners/partnerships.view permissions.