# Readonly role/user unable to view remote cluster index results

**URL:** <https://discuss.elastic.co/t/readonly-role-user-unable-to-view-remote-cluster-index-results/289615>\
**Category:** Kibana\
**Tags:** elastic-stack-security, ccs-cross-cluster-search\
**Created:** [November 18, 2021, 3:28pm UTC](https://discuss.elastic.co/t/readonly-role-user-unable-to-view-remote-cluster-index-results/289615 "2021-11-18T15:28:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jwmocs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jwmocs/32/97273_2.png) [@jwmocs](https://discuss.elastic.co/u/jwmocs)\
**Post date:** [November 18, 2021, 3:28pm UTC](https://discuss.elastic.co/t/readonly-role-user-unable-to-view-remote-cluster-index-results/289615/1 "2021-11-18T15:28:44Z")

</div>

Basically I need a readonly role to simulate the "experimental" _viewer_ role, but limit Kibana privileges to only Analytics\>Discover, and Management\>Dev-tools.  
But my custom readonly role after assigning ALL run-as privileges except for _editor_ and _viewer_ still cannot see the remote cluster result, or run the following remote cluster search in Dev Tool:

```auto
GET my-remote-cluster:remote-index/_search
{
  "query": {
    "match_all": {}
  }
}

```

As soon as I add viewer role, the search is successful. I even copied the exact index privileges from the viewer role edit screen, and I still cannot make my readonly user be able to get the remote cluster results. Anyone know what hidden privileges the viewer role has that I may be missing to be able to do so for my custom readonly role?

---

<div class="post-metadata">

**Author:** ![Yang\_Wang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yang_wang/32/48857_2.png) [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)\
**Post date:** [November 22, 2021, 12:29am UTC](https://discuss.elastic.co/t/readonly-role-user-unable-to-view-remote-cluster-index-results/289615/2 "2021-11-22T00:29:06Z")

</div>

For CCS to work, you custom role needs to be available on the remote cluster.

Please refer to the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/remote-clusters-privileges.html#remote-clusters-privileges-ccs) for details.

---

<div class="post-metadata">

**Author:** ![jwmocs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jwmocs/32/97273_2.png) [@jwmocs](https://discuss.elastic.co/u/jwmocs)\
**Post date:** [November 22, 2021, 2:56pm UTC](https://discuss.elastic.co/t/readonly-role-user-unable-to-view-remote-cluster-index-results/289615/3 "2021-11-22T14:56:22Z")

</div>

Thank you very much, setting up the same role on remote cluster worked for the user's cross-cluster search

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 20, 2021, 2:56pm UTC](https://discuss.elastic.co/t/readonly-role-user-unable-to-view-remote-cluster-index-results/289615/4 "2021-12-20T14:56:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.