Hi,
I have an app with some views/dashboards, and the right to access each view is owned by a specific role :
metadata/default.meta
[views/view1]
access = read : [ admin, access_to_view1 ], write : [ admin ]
export = none
owner = admin
...
The set of dashboards a specific (non-admin) user can see and access is defined through the list of roles given to this user. For example, user "jim" could have the roles access_to_view1 and access_to_view3 in order to see the dashboards view1 and view3 , but not view2 .
My problem is that any user without access_to_view1 is effectively blocked out of the app, since upon login she is redirected to the default home page which is view1 for the app, and Splunk returns a 404 since this user doesn't have the right to access this dashboard.
default/data/ui/nav/default.xml
<nav search_view="search">
<view name="view1" default="true"/>
<view name="view2"/>
<view name="view3"/>
</nav>
The problem is still there if I remove the default="true" part ; I think the default home page is the first view in the list in this case anyway.
How can I manage to have an app in which some users do not have read access to the default home page?
... View more