Configuring Splunk - Implementing Splunk: Big Data Reporting and Development for Operational Intelligence - page 322

• modules : This is where new modules that are provided by apps are stored.
Examples of this include the Google Maps and Sideview Utils modules.
See http://dev.splunk.com for more information about building your
own modules or use existing modules as an example.
Metadata
Object permissions are stored in files located at $SPLUNK_HOME/etc/
apps/$appname/metadata/ . The two possible files are default.meta
and local.meta .
These files:
• Are only relevant to the resources in the app where they are contained
• Do merge, with entries in local.meta taking precedence
• Are generally controlled by the admin interface
• Can contain rules that affect all configurations of a particular type, but this
entry must be made manually
In the absence of these files, resources are limited to the current app.
Let's look at default.meta for is_app_one , as created by Splunk:
# Application-level permissions
[]
access = read : [ * ], write : [ admin, power ]
### EVENT TYPES
[eventtypes]
export = system
### PROPS
[props]
export = system
### TRANSFORMS
[transforms]
export = system
### LOOKUPS
[lookups]