Object permissions are an integral part of securing Apps and their knowledge objects. After all, we don't want the user causing issues in an App you spent hours tweaking, do we? No, that's what I thought. This is where permissions come into the picture. Splunk permissions are role-based, which means that a user needs a specific role (either assigned by Splunk or via external authentication and authorization systems) to read or write the knowledge object. Permissions are controlled within the default.meta and local.meta files in your metadata folder in the App. As per normal Splunk precedence, the local.meta file will override any setting with a matching stanza in the default.meta file.
The configuration structure within the corresponding file is as follows:
[<object_type>/<object_name>]
access = read : [ <comma-separated list of roles>], write : [ comma-separated list of roles>]
Note
The reference for this structure is http://docs.splunk.com/Documentation...
