It is possible to link data connections together. This can have the following benefits.
...
These objects also come from the ‘parent’ data connection so cannot be edited or deleted here.
...
If you see such a structure this is the first indication that you are working on a linked data connection or a ‘child’ connection.
If you now look at the connection tab,
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
It is very important that all of the security related details are configured in the top level organisation. |
Worked Example
I have my 2 organisations - Organisation 1 is the Owning Organisation.
...
Now I switch over to the Tenant Organisation (B)
I now create a user in Organisation B - the tenant organisation.
...
Now I switch over to the Owning Organisation (A)
Then I’ll create the parent data connection in Organisation A. I am going to use [[VARIABLES]] on the role so that different tenants could get redirected to different DB’s / Accounts. I will also check the Can Have Child Connections option.
...
I’ll add some quick content to the data connection.
...
Now I make sure that the data connection Belongs to a specific category (I could leave it at Home - but this is better).
...
Now I create a role - that can control access.
...
I could control the variables on the user subscription, but in this example I am going to use the role. I mark the variables as secure. I don’t want any users to find these values.
...
Next we’ll add a user restriction on the tenant organisation (B) user (B)'s subscription in the owning organisation (A). I’ll put a restriction on so that the user can only view data for the store in Leeds.
...
Now I create a subscription at viewer level for the user in the tenant organisation (B) in this owning organisation (A).
...
I can check this is users / subscriptions
...
Now we grant access to the role in the owning organisation (A) to the subscription of our User (B) from the tenant Organisation (B).
...
Now we will log into the dashboard as the user (B) from the tenant Organisation (B).
We go to the admin panel and the data connection screen.
Now we can create a data connection. Using Data Connection A from the owning organisation (A) as the parent. When I save the connection - it’s connection details go green (actually it passes me straight the data tab because it validates). I am connected to the database but cannot see or control any of the connection details.
...
I will see all of the inherited content.
It’s content is read only for the objects.
...
I can now add to the connection, all whilst having my user restriction enforced and data connection defined by variables. Most importantly all of these details are locked away in my subscription in the owning organisation (A).