2026-10-15
Save Restrictions for Smarty Plugins That Handle Credentials and Secrets
Restrictions on where they can be saved and who can save them have been added to the Smarty plugins that create credentials and the Smarty plugins that read secrets and site settings. If either condition is not met, saving fails with an error.
Affected plugins
| Category | Plugins |
|---|---|
| Create credentials | login / api_mng / api_internal / assign_api_credential / api_token |
| Read secrets and site settings | secret / assign_rcms_conf / gcloud_functions_token |
Restrictions
| Condition | Details |
|---|---|
| Location | Custom functions and batch processing only. They cannot be saved in email templates, content structure trigger settings, extension field templates, CSS/JS, form admin notification subjects and thank-you emails (subject and body), and so on. |
| Saver | Super users only. Content editors cannot save them even if they have the Insert/Update permission for custom functions and batch processing. |
Background
Email bodies, extension field templates, and content structure CSS/JS can be edited with the permission of that module alone. If {secret} or {api_internal member_id=...} could be written there, credentials and secrets would be reachable in a way that does not appear in the permission settings. For this reason, the locations where these plugins can be written have been fixed to custom functions and batch processing, and saving in those two locations has also been limited to super users.
Impact on your usage
- If these plugins were previously written in items other than custom functions and batch processing, saving that item is rejected the next time. Move the processing to a custom function and call it with
{function name="..." var="..."}or{include name="..."}. - Content editors cannot save custom functions or batches that contain these plugins. Staff implementing external API integrations, proxies, and so on will need super user privileges.
- [Test] in the admin panel goes through the same check, so content editors cannot run tests either.
- A custom function or batch that contains these plugins must be saved by a super user even when the edit does not touch the plugins themselves (for example, changing only the execution time of a batch).
- Saving a custom function or batch that contains these plugins via Admin MCP requires the
mcp:adminscope. It cannot be saved with delegated scopes includingmcp:tools.all. - The runtime behavior of processes that are already saved does not change. The restriction applies only when saving and running tests.
There is no advance notice in the admin panel; content editors will notice the restriction only when they click [Update] or [Test]. Please check the permissions of the staff who operate the relevant custom functions and batch processing.
Rollout Timeline
This change was reflected in the October 15, 2026 general release.
Contact
If you have any further questions regarding this matter, please feel free to contact Kuroco Support.
Related documents
Support
If you have any other questions, please contact us or check out Our Slack Community.