Improvements to the overall rights management interface and flow
- More straightforward and accessible rights management system to make it easier and faster to assign rights to your constructs
- Easier management of organization assets
Comments: 5
-
07 Oct, '20
OxdaleCheckboxes instead of dropdown list!!!
-
07 Oct, '20
MegadddThe discord permissions hierarchy where it's just roles and members with those roles, that can allow/inherit/deny the permissions based on how high on the role stack it is, seems like something that should replace the convoluted 4-menu system that leave multiple ways to denote the same effect.
(I.e.: Airlift a good, already working solution from somewhere else and make it your own with a slightly altered look) -
07 Oct, '20
CypsylusYeah I'm not good at understanding how rights work and a little bit visually challenged... I can see stuff but text is hard. Anything to make rights more gui/optionally gui and for those who want it also text would be appreciated. I would love a drag and drop interface or even an out of game drag and drop modeler.
-
10 Oct, '20
DecoyGoatBombThere are so many ways the current system could be simplified. There should be a default tag that is the same name as a policy. It is so uneccesary to need to manually make a "label" tag. Also removing construct tags but replacing it with the ability to add a policy to a construct through the construct list. In future iterations please have basic common sense options as the default then have under the hood advanced stuff as an option.
-
07 Nov, '20
OxdaleIt would be easier if we have access to all the construct belonging to the current entity (player or org) from the RDMS interface. And be able to change tags, names and right access from here.