Hi folks, my company is considering adopting a new orchestration platform and would love to learn more about Flyte. I’m hoping folks here can help answer these questions or point me in the right direction. We have some unique needs because of our organization’s structure. We are a cooperative of 75+ non-profit organizations that share data infrastructure. One of the things we share is our orchestration platform. This means we have some multi-tenant needs that are not typical for a data engineering team. For example, we have a team of data engineers that often build workflows on behalf of member organizations and we also allow member organizations to build their own workflows. As part of our evaluation, we’re curious how we would do the following in Flyte: 1. Manage access to workflows: a. A data engineer builds a workflow for a specific member and wants to grant access to just that member so they can run it manually. 2. Run workflows with custom parameters: a. A data engineer builds a parameterized workflow and wants to share that with several members so they can copy it, add their own member-specific parameters, and set it to run on a custom schedule. b. If we updated the original workflow, would those changes propagate to the member-specific copies? 3. Credential or secrets management: a. Oftentimes, the parameters for our workflows are credentials. Can we upload credentials and share them with a subset of users? Could members add their own private credentials? 4. Impersonate users to help with debugging: a. When a member has an issue, it’s very helpful to impersonate their user so we can see what they see

Hi Erica! Welcome to the Flyte community!

A data engineer builds a workflow for a specific member and wants to grant access to just that member so they can run it manually.

Flyte doesn't offer RBAC. Union.ai, the commercial offering does. I can DM you with the details if this is of interest to you.

If we updated the original workflow, would those changes propagate to the member-specific copies?

If you're referencing the workflow, then yes, the changes would be propagated. The concerning users should update the version, though.

Oftentimes, the parameters for our workflows are credentials. Can we upload credentials and share them with a subset of users? Could members add their own private credentials?

I recommend you to check this thread out.

When a member has an issue, it’s very helpful to impersonate their user so we can see what they see

I'm not sure I understand this. How do you plan to impersonate? cc @Ketan (kumare3)

Thank you, this is all super helpful! • I would love some details for Union.ai. • We currently use a tool that allows us to literally assume another user’s role in the GUI and navigate around + run stuff as though we were logged in as that user. Given our cooperative setup and the vast range of technical skills, this is a feature that saves us a lot of time and reduces a lot of frustration for our members.

@Erica Renée Faulkenberry let me ping you and we can setup a call to help understand more