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

version = 4.3
modtime = 1338420715.753642000
[props/impl_splunk_web/LOOKUP-web_section]
access = read : [ * ]
export = none
owner = admin
version = 4.3
modtime = 1346013505.279379000
...
You get the idea. The web application will make very specific entries for each
object created. When distributing an application, it is generally easier to make
blanket permissions in metadata/default.meta , as appropriate for the resources
in your application.
For an application that simply provides dashboards, no metadata at all will be
needed, as the default for all resources (apps) will be acceptable.
If your application provides resources to be used by other applications, for instance,
lookups or extracts, your default.meta file might look like this:
### PROPS
[props]
export = system
### TRANSFORMS
[transforms]
export = system
### LOOKUPS
[lookups]
export = system
This states that everything in your props.conf and transforms.conf files, and all
lookup definitions, are merged into the logical configuration of every search.