| description |
|---|
Learn how to set up chatflow-level access control for your Flowise instances |
After you have a chatflow / agentflow constructed, by default, your flow is available to public. Anyone that has access to the Chatflow ID is able to run prediction through Embed or API.
In cases where you might want to allow certain people to be able to access and interact with it, you can do so by assigning an API key for that specific chatflow.
In dashboard, navigate to API Keys section, and you should be able to see a DefaultKey created. You can also add or delete any keys.
 (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png)
Navigate to the chatflow, and now you can select the API Key you want to use to protect the chatflow.
 (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png)
After assigning an API key, one can only access the chatflow API when the Authorization header is provided with the correct API key specified during a HTTP call.
"Authorization": "Bearer <your-api-key>"An example of calling the API using POSTMAN
 (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png)
You can specify the location where the api keys are stored by specifying APIKEY_PATH env variables. Read more environment-variables.md