> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/build/manage-workflows/configure-workflow-settings.md).

# Configure digital-organization settings in Duaer

In Duaer, settings include timezone, error handling, and caller policy. After v3 removes “Any workflow”, the check links to the who-can-call section.
## What the settings cover

Each digital organization has its own settings: timezone, timeouts, whether to continue on error, and who may call it. Changes apply to this digital organization, not the whole instance. Instance defaults are under [workflows environment variables](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/workflows.md).

## Who can call this digital organization <a href="#this-workflow-can-be-called-by" id="this-workflow-can-be-called-by"></a>

The caller policy decides which digital organizations may Execute Sub-workflow against it. v3 removes “Any workflow”. If it is still set so anyone can call, the instance check opens this section.

Switch to the same project, a named list, or another option that remains. Sub-organizations are under [subworkflows](/flow-logic/subworkflows.md).
## Questions

### What does “who can call this” mean in Duaer digital-organization settings?

The caller policy: which digital organizations may Execute Sub-workflow against it. v3 removes “Any workflow”. If the instance check finds that option still in use, it links to this section.