According to http://www.splunk.com/base/Documentation/4.1.4/Admin/Apparchitectureandobjectownership
it sounds like if a user has the ability to promote saved searches and other objects to the App level, they should be able to promote all objects on that list, including dashboards/views.
I'm currently building some dashboards under 4.1.3 as a regular user. I was able to save searches and search macros and then set them to be App-visible.
When I created a view and try to promote it, I get a red error bar: Splunk could not update permissions for resource data/ui/views Client is not authorized to perform requested action
Bug, misconfiguration, or misunderstanding?
It depends on the app-specific permissons, which are controlled by $SPLUNK_HOME/etc/apps/<app_name>/metadata/default.meta
For example, in the search app, only admin users have write permissions for views -
### VIEWS
[views]
access = read : [ * ], write : [ admin ]
If you change the permissions so that the user role has write-access, then you should be able to promote your views.
+1 vote Mick
If you don't vote up my answer, nobody knows how smart I am. Click the "up" arrow if you find the answer useful people!
Wow, smart guy, that Mick.
It's 4.1.3 on solaris, for the record.