Workflow Sharing Configuration
Last updated
Last updated
By default, a shared Workflow does not run under your API Keys and credentials. This means that it does not consume your usage limits and replaces any credentials like OpenAI API Key on your blocks as input parameters the user should provide. You can change this behavior by changing sharing configurations:
This is useful when you want to share a Workflow containing a private Model - since the default behavior is not to run under your API key, a Workflow containing a private Model will fail to execute - so you change that to allow a protected run: it will affect your usage limits, but your API Key and model data will always be private.
To do so, go to the Run access section and change it to allow anyone to run the Workflow.
This option is only available when a private Model is detected in the workflow steps.
This configuration side effects are:
Any previews run under the shareable link will affect your Wokflow usage.
Your private Models data and your API Key will always remain private.
This is useful when you want to share a workflow that has any step with credentials (LMM, OpenAI, Anthropic, etc.) and let people securely use your own credentials to make it easier for them to try your Workflow - your credentials won't be exposed and will be redacted on any client-facing data.
To do so, go to the Credentials section and change it to allow users to execute the Workflow with your hidden credentials.
This option is only available when a step that needs credentials is detected in the workflow.
This configuration side effects are:
Any previews run under the shareable link will affect your specific credential usage limits (e.g. OpenAI Api Keys).
Your credentials values will always be private and are redacted from any client-facing data.
Here's an example of a Workflow that runs under a hidden OpenAI API Key to run a License Plate detection + OCR. Give it a try!
