This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6
Objects in an App have access controls set by role. Use access controls to set which users can read and write to which objects. Currently, object types include:
You can set permissions on a per-object basis in Splunk Manager. Follow these instructions:
Use default.meta to set read and write permissions for all the objects in your App. Follow these instructions:
$SPLUNK_HOME/etc/apps/<app_name>/metadata/default.meta.
[/<owner>/<App>/<object_type>/<object_name>] access = read : [ <comma-separated list of roles>], write : [ comma-separated list of roles>]
You can set permissions on a per-object basis by explicitly naming the object. For example, this entry gives the admin role read and write permissions for the "Splunk errors in the last 24 hours" saved search:
[/nobody/search/savedsearches/Splunk%20errors%20last%2024%20hours] access = read : [ admin ], write : [ admin ]
You can also set permissions for all objects of a given type. This entry grants read permissions to everyone and write permissions to admin and power roles for all event types in the App:
[/nobody/search/eventtypes] access = read : [ * ], write : [ admin, power ]
By default, objects are only visible within the App they were created in. So if you create an event type in your helloworld App, it will show up within that App. To make an object available to all Apps, add the following line to the object's entry in default.meta:
export = system
For example:
[/nobody/helloworld/eventtypes] access = read : [ * ], write : [ admin, power ] export = system
This will make all event types in helloworld viewable in every App in your Splunk install.