Short answer: yes — if they’re just an account-level “Member”, they won’t be able to schedule deployments or add triggers unless they also have the right workspace role. In Prefect Cloud 3.x: - Scheduling a flow (adding/editing a deployment schedule) requires the workspace permission “Create and edit deployments” - Creating/editing triggers (Automations) requires “Create, edit, and delete automations” - Those permissions are included in the workspace roles: Developer and Owner - Viewer, Runner, and Worker do not have these permissions What to do: - Check the user’s workspace role in the specific workspace. If they’re not a Developer or Owner, update their workspace role accordingly. - UI path: Workspace → Settings → Members → change their role to Developer (or Owner). - On Enterprise, you can create a custom workspace role that grants just those permissions. Refs: - Manage roles (Cloud) - Schedules - Automations (creating/editing) If you can share the user’s current workspace role, I can confirm exactly what they can/can’t do and the minimal change needed.