[ https://issues.jboss.org/browse/WFLY-490?page=com.atlassian.jira.plugin.s... ] Ben Schofield commented on WFLY-490: ------------------------------------ This is greatly needed in most large enterprises. At minimum I would be looking for 1) read only - (read) 2) administration - full access (read,write,execute) 3) operation - can execute operations but can not change configuration. Support personnel would would use this role heavily to start/stop servers, purge connection pools, move jms messages, trigger heap and thread dumps, etc. (read,execute) 4) configuration - a role for updating configurations. Useful for provisioning and configuration automation systems such as puppet and chef. (read,write) If read,write,execute permissions can be mapped to the dmr and reflected in the management console that would put wildfly and consequently future EAP releases a step above more expensive competitors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira