# Set Discoverable in Quick Sight programatically **URL:** \ **Category:** Q&A\ **Tags:** dashboard, embedding, developer, sharing, quick-sight\ **Created:** [March 16, 2023, 4:21pm UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160 "2023-03-16T16:21:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Hrocho](https://avatars.discourse-cdn.com/v4/letter/h/85e7bf/32.png) [@Hrocho](https://community.amazonquick.com/u/Hrocho)\ **Post date:** [March 16, 2023, 4:21pm UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160/1 "2023-03-16T16:21:49Z")
Is it possible to share a dashboard via CLI with “Discoverable in Quick Sight” disabled? Use case: We provide a default set of dashboards that we share with our clients by adding them to the group. Then we make the dashboards accessible on our website using the embedding dashboard feature. This works just fine. But we want to add them the ability to create their own dashboards via the embedding authoring feature. But we do not want them to see the default set of dashboards there. So it is possible to disable “Discoverable in Quick Sight” in the default dashboards programmatically? I refer to this feature in the QS console UI: ![Screenshot 2023-03-16 at 17.19.30](https://d1wl4jav5dp96l.cloudfront.net/original/2X/5/514113d52dc6ca9a0e7966ac7bb6bab547fca2ab.png) ---
**Author:** ![Max](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/max/32/2288_2.png) [@Max](https://community.amazonquick.com/u/Max)\ **Post date:** [March 17, 2023, 2:24pm UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160/2 "2023-03-17T14:24:50Z")
It doesn’t seem like there is the ability to do that via the cli now. However, after looking at the api calls it looks like it makes the same api call with a slightly different payload. Here is the api call to share with everyone in the account. ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/5/5465c4c9b1f72e548415c53e96cdfa03d46db2b6.png) And here is the one to make it discoverable in quicksight. ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/8/82ccfb8e75d1f21c341ae3a1aa978bd2741a31af.png) The first one grants like permissions. The second grants permissions. Maybe something to work with. ---
**Author:** ![Hrocho](https://avatars.discourse-cdn.com/v4/letter/h/85e7bf/32.png) [@Hrocho](https://community.amazonquick.com/u/Hrocho)\ **Post date:** [March 20, 2023, 5:37pm UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160/3 "2023-03-20T17:37:03Z")
Thank you. I’ve tried it, but unfortunately, the LinkSharing is working just with namespaces. Even if it is written in the documentation, it should also work with users and groups. ![Screenshot 2023-03-20 at 18.30.33](https://d1wl4jav5dp96l.cloudfront.net/original/2X/f/f76fc875831742c8672865c5542a80178767e2ed.png) I got: An error occurred (InvalidParameterValueException) when calling the UpdateDashboardPermissions operation: Principal arn:aws:quicksight:us-east-1:133301937439:group/abc is not allowed in Link Permissions. An error occurred (InvalidParameterValueException) when calling the UpdateDashboardPermissions operation: Principal arn:aws:quicksight:us-east-1:133301937439:user/xyz is not allowed in Link Permissions. or does the group or user need to be somehow configured? ---
**Author:** ![Hrocho](https://avatars.discourse-cdn.com/v4/letter/h/85e7bf/32.png) [@Hrocho](https://community.amazonquick.com/u/Hrocho)\ **Post date:** [March 30, 2023, 9:13pm UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160/4 "2023-03-30T21:13:55Z")
@Max Any thoughts? I’ll appreciate it if you could shed light on my issue with using other Principal than namespace. ---
**Author:** ![Max](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/max/32/2288_2.png) [@Max](https://community.amazonquick.com/u/Max)\ **Post date:** [March 30, 2023, 9:31pm UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160/5 "2023-03-30T21:31:16Z")
have you tried using the default namespace? ---
**Author:** ![Hrocho](https://avatars.discourse-cdn.com/v4/letter/h/85e7bf/32.png) [@Hrocho](https://community.amazonquick.com/u/Hrocho)\ **Post date:** [April 3, 2023, 8:09am UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160/6 "2023-04-03T08:09:07Z")
It is working with the namespace. I didn’t try the default namespace, but my custom one works fine. Unfortunately, we need to work with groups, not in the scope of the whole namespace. Another thing seems to make “Discoverable in Quick Sight” function unsuitable. We are associating dashboards with groups based on dashboard categories, and then we add users to groups based on our business logic. Then we use the `search-dashboards` function to get the list of available dashboards. We present this list to a user, and they can choose which one they want to see in the embedding mode. But flagging a dashboard with not “Discoverable in Quick Sight” also disappears in the `search-dashboards` function result. ---
**Author:** ![Max](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/max/32/2288_2.png) [@Max](https://community.amazonquick.com/u/Max)\ **Post date:** [April 3, 2023, 5:35pm UTC](https://community.amazonquick.com/t/set-discoverable-in-quicksight-programatically/11160/7 "2023-04-03T17:35:40Z")
I would look to open up a support case. Here are the steps to [open a support case](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html). If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account.