Thanks for the comment <@UFG3USN8K> :slightly_smiling_face:\n\n\u2022 Regard your first bullet, when you write Permission model, it is little bit confusing, I\u2019m not sure if you mean Security models, Permission model or resource/view menu model.\n\u2022 Regard the auto CRUD, the implementation should not change the design. In java, spring have that ability, and there is spring for python so I\u2019m sure a solution for it will be found, worst case we have to implement dynamic association by join.\n\u2022 Regard db constraint - if you can write a constraint for it at DB level (worst case, it can be done by trigger), it should be written at SQLAlchemy level. if there is a feature we can do at DB level but not at SQLAlchemy level, we can announce of missing feature and starting with SQLAlchemy contribution.\n\u2022 Regard your second bullet - yes - if it a little bit confusing, we can think of can_access.dashboard* or dashboard[all] , it doesn\u2019t really matter.\n\u2022 third bullet - we agree with you, and I have ideas how to do it more efficiently then create a role for one user \u201cdashboad_x_owner_role\u201d but let\u2019s focus on it later.\n\u2022 Your first note - true, that what we think too.\n\u2022 BTW I think the discussion should be at FAB level, probably not only superset cases.