@Marvin, I have flows that are protected by own authentication protocol, i would like to make it so that i can have third parties activate flow runs and observe the progress so as to act as a reporting backend. what examples and best practices are there to allow such a connection?

hi @David - not sure where marvin was here but I think the easiest way to answer this question would be • you can create deployments that are trigger-able through the REST API • you can set up some layer between your 3rd party and the REST api that looks at permissions and stuff and

POST /create_flow_run_from_deployment

etc accordingly are you intending to expose the dashboard to third parties as well? or just the ability to run work via your auth protocol

thanks for jumping in. I’ve played around and had success with creating lambdas to trigger flow runs in AWS using the REST api provided by your team. i was wondering if Marvin had any resources/best practices pertaining to this type of work. are you intending to expose the dashboard to third parties as well? not really, i have set of deployments that I want to provide and i currently use one workspace. If i understand it correctly, you provide the option to create bespoke workspaces to limit deployment resources which i think would the best solution if I was to expose the full dashboard.