I am not authoritative on this, but I think user1 should not have any privileges for the .kibana index. Dashboard entries and other kibana objects are managed by kibana itself, using the .kibana index, but not in the way you have pointed out. That is, other types of privileges, and not document level security ones, are used to limit scope. This privileges are managed by the kibana process itself (stored in the .kibana index) and atm they don't not rely on elasticsearch.
I suppose what you are looking for is Kibana Spaces . Have you tried it? This is the proper way to authorize on kibana objects.
Hope that helps to get a perspective on things,
Albert
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.