Most of these checks need to have either eventId or chapterId passed. Otherwise only check will be done only on the instance permissions.

in some cases (mostly "add new" something buttons), we will have code that looks like this, which will create an array of the permissions.

data.dashboardEvents.map(({id})=>checkPermission(
    user,
    Permission.EventCreate,
    {id}
  ));

What are your thoughts about keeping the instance's permission for most cases except "create new event", and "create new venue" 🤔? Because these are the only ones currently, that admins interact with

For current roles that would be enough. But to give ability to add custom and more granular role permissions, I think it would be better to pass the event id and/or chapter id to checkPermission as well. Even if so far these permissions would be only on some instance roles.

Last question 👍, do I add the ability to filter the data that aren't editable in this PR?

Edit: we don't have the rule of organizer, so thinking of features for them isn't necessary currently.