You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What we need to achieve is that when clicking on a calendar event, the context menu should display actions based on the user's policies/permissions for that particular model type. For example, a user with "view_activity" but not "edit_activity" permissions should only see the view action when clicking on an Activity event(model).
I'm not sure if there's a way to access the event model type before the record is loaded - if there is, I'd appreciate guidance on how to implement this. This would allow proper integration with Laravel's policy system for granular permission control.
Currently calendar context menu actions (view/edit/delete) are always shown regardless of user permissions. This leads to two issues:
Actions are visible even when users lack permissions
The getEventRecord() method returns null on initial load, making it impossible to check model type for permission validation
What feature would you like to add?
What we need to achieve is that when clicking on a calendar event, the context menu should display actions based on the user's policies/permissions for that particular model type. For example, a user with "view_activity" but not "edit_activity" permissions should only see the view action when clicking on an Activity event(model).
I'm not sure if there's a way to access the event model type before the record is loaded - if there is, I'd appreciate guidance on how to implement this. This would allow proper integration with Laravel's policy system for granular permission control.
Currently calendar context menu actions (view/edit/delete) are always shown regardless of user permissions. This leads to two issues:
getEventRecord()
method returns null on initial load, making it impossible to check model type for permission validationWe need a mechanism to:
Example of current limitation:
The text was updated successfully, but these errors were encountered: