Add permission requirements

Lukasz Balcerzak avatarLukasz Balcerzak created an issue

I think livesettings are great idea, however giving away possibility to change settings for every staff member is something I'm not really feel good about. If changes were stored maybe it won't be that bad (well, we could at least blame someone but in my view it is better not to allow to make changes at the first place).

Or maybe I'm totally missing something? Documentation is needed too as well...

Comments (3)

  1. Chris Moffitt

    I do agree that finer grained permissions would be useful - if you have ideas or patches that would be helpful.

    As far as documentation, I agree it's needed, we just need the time to do it. If you have a start or ideas how to structure, let us know.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.