Following documentation it says it should inherit the module permissions if no other permissions have been set but it doesn't seem to inherit to all the levels.
This happens for privileges (adding, editing, etc), but not view access. View access works via a series of successive barriers rather than inheritance.
You've found a bug. When it imports categories it is not setting default permissions to view. We'll fix that.
In theory you should be able to expand it all in the Permission Tree Editor, and use Shift+Click'ing to multi-select and then batch set view permissions that way.
I've never tried it with hundreds, I fear it might get very slow or break some limits, but 20 at a time should work.
Was I helpful?
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.