Making access to reusable workflows clearer

content/actions/using-workflows/reusing-workflows.md

@@ -59,6 +59,18 @@ A reusable workflow can be used by another workflow if any of the following is t
 - The called workflow is stored in a private repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion ghes or ghec %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-organization)" and "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-from-your-private-repository)."{% endif %}
 {% endif %}
 
+In summary, for the called workflow to be reachable by the caller workflow, the repository's visibility must be as shown in the table below.
+
+| Caller repository | Accessible workflows repositories |
+|----|----|
+| `private` | `private`, `internal`, and  `public` |
+| `internal` | `internal`, and `public` |
+| `public` | `public` |
+
+Additionaly, please note that the **Actions permissions** on the caller's repository Actions settings page must be configured to allow the use of actions and reusable workflows.
+
+Furthermore, except for a public repository, also note that the **Access** policy on the called workflow's repository Actions settings page must be explicitly configured to allow access from repositories in the organization or repositories in the enterprise.
+
 {% data reusables.actions.actions-redirects-workflows %}
 
 ## Using runners