{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":4226,"path":"build-workflows/workflow-studio/grant-access-flow-apis.md","title":"Create a client callable flow, subflow, or action","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a client callable flow, subflow, or action\n\nEnable a client script to trigger a flow, subflow, or action.\n\n## Before you begin\n\n-   Role required: security\\_admin\n-   Consider the implications of making a flow, subflow, or action client callable, such as whether it exposes protected data or bypasses validation logic.\n\n## About this task\n\nBy default, the flows, subflows, and actions can only be called by the FlowAPI within a server script. Flow and action designers can make individual flows, subflows, or actions available to client calls by enabling the **Client callable** option during the design process.\n\n## Procedure\n\n1.  Elevate privileges to security\\_admin.\n\n2.  Navigate to **System Security** > **Access Control \\(ACL\\)**.\n\n3.  Click **New**.\n\n4.  Create an access control.\n\n    |Field|Description|\n    |-----|-----------|\n    |Type|client\\_callable\\_flow\\_object|\n    |Operation|execute|\n    |Admin overrides|Selected|\n    |Name|Enter a name for the ACL.|\n    |Requires role|Create a role to provide access to the APIs. For example, create a flow\\_api\\_access role.|\n\n5.  Assign the role to the user you would like to grant access to.\n\n6.  Enable a client script to trigger the flow, subflow, or action.\n\n    1.  Open the flow, subflow, or action you want to make client callable.\n\n    2.  In the **More Actions** menu, select **Manage security**.\n\n    3.  Select **Callable by Client API**.\n\n    4.  Add the access control record created earlier to the **ACLs** field.\n\n    5.  Click **Update**.\n\n\n## Result\n\nThe user with the designated permissions can trigger a client callable flow, subflow, or action from a client script using the GlideFlow API.\n\n"}}