Assuming that the microflow is only used as a sub-microflow: <\/p>\n\n\n\n Compliant example:<\/strong><\/p>\n\n\n\n Assuming that the microflow is only used as a sub-microflow:<\/p>\n\n\n\n How to solve this violation?<\/strong><\/p>\n\n\n\n When you are working on solving this violation, but you get a message in Studio Pro that states that the specific microflow does need permission, make sure that you have applied the correct naming convention: <\/p>\n","protected":false},"featured_media":0,"parent":96,"menu_order":22,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-594","docs","type-docs","status-publish","hentry"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/docs\/594"}],"collection":[{"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=594"}],"version-history":[{"count":11,"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/docs\/594\/revisions"}],"predecessor-version":[{"id":2453,"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/docs\/594\/revisions\/2453"}],"up":[{"embeddable":true,"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/docs\/96"}],"next":[{"title":"Published Rest and Web services should require authentication","link":"https:\/\/sdf-docs.clevr.com\/?docs=acr-rules\/security\/publishedserviceauthentication","href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/docs\/1369"}],"prev":[{"title":"Microflow called from the client should apply entity access rules","link":"https:\/\/sdf-docs.clevr.com\/?docs=acr-rules\/security\/microflowentityaccess","href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=\/wp\/v2\/docs\/249"}],"wp:attachment":[{"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=594"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/sdf-docs.clevr.com\/index.php?rest_route=%2Fwp%2Fv2%2Fdoc_tag&post=594"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/sdf-docs.clevr.com\/wp-content\/uploads\/2020\/01\/image-41.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/sdf-docs.clevr.com\/wp-content\/uploads\/2020\/01\/image-40.png\")
<\/figure>\n\n\n\n
– If the microflow is used directly from a page, the microflow should not start with SUB<\/em>. Read through our documentation<\/a> to select the correct naming convention for the function of your microflow. If you use the microflow both from a page and as a sub-microflow somewhere else in the project, we advise creating a microflow that calls the sub-microflow, and that you handle the permission there.
– If a sub-microflow is also called from a nanoflow, we recommend using a special Nsub_ <\/strong>wrapper (with permissions) in the nanoflow that calls the SUB_microflow (with no permission) that is also used as a regular sub-microflow. Read more about this naming convention here<\/a>.
– If the specific microflow is used from the project navigation, we recommend changing the prefix to Nav_<\/strong>. Read more about this naming convention here<\/a>.<\/p>\n\n\n\n