This skill doesnt have an ACL<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Customer is not able to add the ACL to the custom skill, and subsequently encounters an issue where they do not have the option to click on 'Add ACL'. Resolution : Upgrade the UI Builder to the latest version to ensure compatibility with current security protocols and feature implementations, as older versions may lack support for ACL management interfaces or contain bugs affecting functionality. Repair the plugin sn-canvas-chrome to address potential corruption or configuration errors that could be preventing proper rendering of the 'Add ACL' option or causing instability in the skill setup process. This step ensures the plugin functions as intended within the application environment. Make sure you are adding the skill in the right application scope, as ACL permissions are scope-dependent. You can verify the scope in sn_nowassist_skill_config to confirm alignment with the intended application context, ensuring that the skill is registered under the correct environment or module where ACL management permissions are valid.