Hi Folks - I am wondering about best practices for managing the following use case. Our organization has multiple end users from different companies, all of which are our customers. We would like to provide an experience login for each user and limit each user to see only those devices that per…

This is a great question, and is a reference architecture we should definitely document. Here’s a high-level overview of our recommended best practice for deploying a multi-tenant app from within a single Application Experience. We recommended a single application to own all devices for all clien…

@Brandon_Cannaday Great guidance. Yes having documentation and example would be a big help for multi tenant. Do you also have any recommendations on managing client-to-client variation in Dashboards and Pages (or possibly workflow variations for alerts) to reflect client preferences? I’m thinki…

[image] paul_wareham: Great guidance. Yes having documentation and example would be a big help for multi tenant. I also would love to see this, it’s my application setup also.

Generally custom Data Tables are a great place to store any configuration differences between clients. Then when a workflow runs, you can query the required row of configuration data based on the device’s “client” tag or the user group. The workflow can then perform different operations based on tha…

Hey @Brandon_Cannaday I was wondering if you had any suggestions on extending that reference architecture to include Experience Users who might belond tomore than one Client? I.e. a client might have multiple locations and some client users might need to certain all assets and other client users m…

I might recommend switching to User Tags instead of User Groups for this. This way you can add a “client” tag and a “location” tag. Tags, like Groups, will be automatically available in the workflow payload. Then in the Get Device node, you can do a Tag Query for all devices that have a “client” an…

@Brandon_Cannaday I’ve tried everything I can think of to use standard dashboard pages to automatically display a list of all devices an experience user has access to. I don’t think this is possible with any of the existing blocks. Can you correct me if I’m wrong? I think I would need a Custom …

I’ve elaborated on this architecture with step-by-step instructions here: [image] Display a list of devices based on experience user group Help I’m attempting to use an experience dashboard page to generate a list of devices matching a device tag value. The value is obta…

[image] Brandon_Cannaday: We recommended a single application to own all devices for all clients. This application also hosts your end-user experience. I know this is a 2 yr old topic, but I’m running into this type of ‘structuring’ now as we speak…so, am I understanding correctly you’d recom…

Hey @Jose_Cruz , I believe your approach is correct: different applications per “project”. It sounds like your projects are quite a bit different between each client. The recommendation for a single application is when you’re delivering an identical solution to multiple customers. An example would …

Managing experience users for different clients

Help

Brandon_Cannaday May 29, 2018, 6:02pm 9

I’ve elaborated on this architecture with step-by-step instructions here:

Topic		Replies	Views
Get list of all users who have access to a device within an experience Help experience , workflow	3	1164	July 21, 2020
Events Get - experienceUserId: Cannot resolve to more than 1000 devices Help experience , workflow , rest-api , losant-api , events	1	524	October 18, 2021
Show dashboard data based on which user is logged in Help dashboard , workflow , device	1	524	August 6, 2021
Experience views and multiple dashboards Help experience , dashboard , devices	5	1013	September 1, 2021
Dynamically create experience dashboards showing state of all devices for the logged in user Help	4	1954	July 30, 2018

Managing experience users for different clients

Related topics