Suggestion - Save permission settings for non-active modules
I would like to make some modules, like Ads, available for my community one-by-one, after it got used to the main core modules. Therefore I would like to prepare settings for different membership levels in advance. But whenever I set a module to non-active in Studio, permission settings get lost and I have to set them up from new when re-activating them. Please consider, if changes in membership level permissions for non-active modules can be saved to the DB, even when module is set to inactive.
-
Hello @thomlin !
As the records permissions levels and left limits of the members may reach huge values then it may drive to errors easily. Sp the resetting permissions manually will be safer...
-
I'm not sure, if we're talking about the same thing, Leonid. I mean permission levels and switches for on and off for different allowed tasks (create new, delete, etc.). What's the necessary space for a boolean? A byte? If I have, for instance, 10 levels and a module like Ads, with maybe 10 different permission tasks, that would give a 100 bytes to save to the db. That would be acceptable, wouldn't it? Or did I get you wrong?
-
Got it now. You mean, settings of the allowed actions forms would have to be saved with the on/off values, too. Ok, I understand that this might blow up the db probably too much.