Design role boundaries first
Before inviting teammates, decide who needs billing visibility, who can edit automations, and who only needs operational execution access. This avoids overexposing sensitive routes later.
| Role focus | Typical access | Risk to watch |
|---|---|---|
| Operators | Execute flows and manage files | Unreviewed changes to shared presets |
| Managers | Read analytics and team state | Broad access without ownership |
| Admins | Billing, settings, and user actions | Credential sprawl |