Question about client dashboards, multitenancy v data permissions

  • 17 February 2022
  • 1 reply

Hi there!

I'm a non-data person scoping out GoodData for a service we're starting and planning to scale.

It would involve being able to share data to different clients, with the core data structures being the same for each client. This data would mainly consist of the client's staff details and how many of our training sessions they're booking into and attending in the first instance. Ideally at some point we might want to tweak the exact visualisations shown to each client, but we'd never have differing structures/logical models. We would also be relying on manual upload of CSVs at the start.

Initially the concept of multitenancy seemed to fit, but that seems to just be for non-CSV data sources. Is that right?

From what I can see the only option this leaves for segmentation of data is data permissions. The implication through a lot of your documentation is that data permissions are a solution for different internal users (whereas for different external users you'd use different workspaces, with multitenancy to make it easier if the underlying data comes from the same place). Is that correct, and if so, is it a preference or must?

Appreciate any thoughts/advice/corrections!


Best answer by Jan Kos 17 February 2022, 01:40

View original

1 reply

Userlevel 1

Hello Erdin,

for your first question, multitenancy (In Gooddata's term Life Cycle Management) can be used with both database data sources or CSV object storage (even CSV uploads). To differentiate which data should go to which client, Client ID is used in data loading. Second approach you are mentioning is possible too even for external users, but usual approach is managing separate client workspaces via Life Cycle Management. In case of single workspace data permissions must be used to make sure every user see data which he/she suppose to.