ld-permissions

To add a new permission scope in Lightdash using CASL, you centralize the scope definitions within the authorization guidelines. This involves updating the role mappings and CASL integration to enforce the new access control rules across both backend and frontend workflows.

A user lacks Dashboard access in Lightdash when their assigned role does not include the required CASL permission scopes or conditions. Debugging involves verifying the user's role mappings and checking the enforced authorization rules within the project context.

CASL authorization in Lightdash works by centralizing scope definitions and role mappings to enforce access controls. It applies these permission rules consistently across both frontend and backend code paths to ensure secure resource management.

No external installation is required to manage custom roles in Lightdash. The authorization guidelines reference existing code locations like packages/common/src/authorization to apply role management and CASL controls directly.

Yes, you can test CASL permission enforcement in both server and client code paths. The centralized authorization guidelines enable building new permissions and verifying enforcement scenarios across the entire Lightdash workflow.

The best way to design custom roles for Lightdash projects is by using the centralized CASL authorization guidelines. This approach streamlines access control design by mapping scopes to specific roles and verifying enforcement conditions.