<#555 [Feature] Access control on who can run/view...
# flyte-github
a
#555 [Feature] Access control on who can run/view workflows Issue created by senthilnathan23 Motivation: Why do you think this is important? We want to have better access control over who can run/view workflows. Currently this is blocker to create any critical pipelines on Flyte. Goal: What should the final outcome look like, ideally? Flyte UI/CLI: Should allow certain list of users to view/run the workflows. This could be configured through the code. Describe alternatives you've considered There are no alternatives at this point to overcome this. Flyte component ☑︎ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline N/A Additional context N/A Is this a blocker for you to adopt Flyte This is a blocker for us to start using Flyte for our critical data pipelines. flyteorg/flyte