New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request : Restrict user access to everything but dashboards #8730

Open
fetanchaud opened this Issue Oct 19, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@fetanchaud

fetanchaud commented Oct 19, 2018

Hi !

Not all companies are ready to deliver data as a service yet.

So what about restricting registered user access to everything but dashboards ?
This could be a per group configuration.

Dashboard in that mode should behave like when shared with a public link (no way to see the underlying records)

Thank you !

@mazameli mazameli added the Proposal label Oct 24, 2018

@mazameli

This comment has been minimized.

Contributor

mazameli commented Oct 25, 2018

To clarify, I'm assuming this would also mean:

  • hiding the Ask a question button
  • hiding the Our Data section on the homepage
  • hiding the Data Reference, so that users couldn't navigate to tables from there

Additional questions:

  • Would users be able to click on a question in a dashboard to see it in greater detail? If so, I assume you'd expect the query builder bar (or SQL editor) to be hidden?
  • Some dashboards might contain saved questions that are raw data. Would you expect those questions/cards to be hidden?
  • Should users be allowed to browse collections, but only see dashboards? Or would you expect them to be able to view saved questions and pulses, too, as long as they couldn't modify the saved questions or see the underlying records? Would you want them to be able to see saved questions that are raw tables?
  • Relatedly, would you expect Search results to be limited to just dashboards?
  • Would you also want to prevent users from creating new dashboards (or pulses)?

Thanks for your thoughts!

@fetanchaud

This comment has been minimized.

fetanchaud commented Oct 25, 2018

Hi @mazameli,

Our use case is :

  • No corporate web site
  • Will to provide access to only a subset of company data or aggregates - yes, it still happens :-(

So we are looking for a way to disable any discovery possibility, but you are right, giving access only to dashboard sounds much too restrictive.

Maybe an interesting feature could be to prevent user from editing the question itself (table, filter, view, group, columns in raw mode), but to let him choose the right rendering (bar, pie...).

That way user could create copies of predefined questions with the right rendering,
and even create dashboards based on these copies and any other available question (without the 'see the underlying records' feature).

These tailored questions and these dashboards could be saved only in personal collection.

This could be achieved with a group's attribute disabling all the discovery features,
and altering the 'View Collection ' right accordingly ?

But It might be a lot of work. What do you think about this idea ?

To clarify, I'm assuming this would also mean:

* hiding the `Ask a question` button

* hiding the `Our Data` section on the homepage

* hiding the `Data Reference`, so that users couldn't navigate to tables from there

Additional questions:

* Would users be able to click on a question in a dashboard to see it in greater detail? If so, I assume you'd expect the query builder bar (or SQL editor) to be hidden?

NO

* Some dashboards might contain saved questions that are raw data. Would you expect those questions/cards to be hidden?

NO

* Should users be allowed to browse collections, but only see dashboards? Or would you expect them to be able to view saved questions and pulses, too, as long as they couldn't modify the saved questions or see the underlying records? Would you want them to be able to see saved questions that are raw tables?

YES, ONLY DASHBOARDS

* Relatedly, would you expect Search results to be limited to just dashboards?

* Would you also want to prevent users from creating _new_ dashboards (or pulses)?

YES

Thanks for your thoughts!

@fetanchaud

This comment has been minimized.

fetanchaud commented Oct 26, 2018

Could be related to #8773

@tlrobinson

This comment has been minimized.

Member

tlrobinson commented Nov 12, 2018

If I understand correctly, this is already possible by creating a group with no "Data permissions". Make sure to revoke all permissions from the "All Users" group too. You can also just give the group "View" access to specific collections if you want to restrict them to a subset of dashboards/questions.

We even do hide the buttons/sections @mazameli mentioned in his first comment if the user doesn't have any Data permissions:

screen shot 2018-11-12 at 10 14 21 am

As far as not allowing the user to click into a question from a dashboard, I don't really see the purpose of that as it doesn't expose any new data, it's just showing a fullscreen version of one question. We already hide the query builder bar too.

@fetanchaud

This comment has been minimized.

fetanchaud commented Nov 13, 2018

Hi @tlrobinson,
Yes Metabase already do the job, thank you !

There is just one remaining issue : #8700

Removing all data access rights leads to empty dashboard filters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment