We have moved to GitHub Issues
Created by Benjamin Carleski 02 Aug 2018, 14:53:46 Updated by Jason Prothero 08 Aug 2018, 16:25:55
When you have a separate development team who works primarily in Visual Studio, with a source code control system, and uses automated processes to move changes into different environments, it would be very helpful to be able to restrict the ability to make changes to document types, or macros, or data types, in environments that should be configured by the automated processes. These could be QA, staging, or production environments.
This could be done either by creating a user permission that grant read vs read/write permission to each of the tabs on the back-end, or by granting read vs read/write permission to each of the various types of data that could be changed. The former would likely be simpler to implement, but the later could be more extensible to allow for custom data types introduced by packages, and allowing developers to take advantage of this new feature.
Hi @firstname.lastname@example.org - while I understand the idea behind this, we would instead encourage you to never give access to the developer/settings/etc sections to any users apart from maybe a dedicated admin account. If you're using automated systems there shouldn't be a reason for anyone to access those areas other then on local dev copies.
What about Dictionary Items in the Settings? Perhaps those should be moved to a new section?
Type: Feature (request)
Backwards Compatible: True
Due in version: