General
Set the flow’s core identity and defaults.Steps Visibility
Controls whether requesters can see individual steps as their task progresses.- Visible to Requester
All steps are visible by default. Individual steps can still be hidden.
Permissions
Controls who has access to the flow and what they can do.Roles
Add users by clicking + Add and selecting Everyone, specific members, or groups. Remove access with the × next to an entry, or change a role from the role dropdown.
This is the general flow-access role set. Task-level roles (Owner, Assignee) are separate — see Roles and Permission Levels.
Field edit permissions
Choose a default for every field in the flow:- All Fields Need Approval — every field requires approval before a change takes effect, unless overridden at the field level
- No Approval Required — every field can be edited immediately, unless overridden at the field level
Notifications
For each lifecycle event, choose who’s notified: Owner, Assignee, Requester, or All.Naming
Build the filename template used for documents this flow produces.- Task Title — Chamelio names tasks automatically. Choose Agent (an AI-generated title from the document’s content, guided by your own prompt and
@tokens like@Workflow name) or Manual (a fixed template you build with@fields, with a live preview). - Version Preferences — control how stored versions are named during the negotiate step.
- Signed Document Preferences — control how contracts are named once signed.
Reminders
Automatic nudges based on a task’s status and deadlines.- Who to remind — applies across all reminder types below
- Days in step — remind assignees after a task has sat in a step for N days, on a repeat cadence
- Task not assigned — alert when a task has no assignee, after a configurable delay
- Task overdue — escalate when a task misses its due date