Enable Flow Design for Private vs Public Items

TL;DR

• Mapped enabling behavior across Global (Explore) and Project namespace scopes for private and public items, comparing first pass vs second pass UX
• Private items can only be enabled in the owner/managing project, so first pass uses a modal with project pre-selected, second pass removes the modal entirely
• Public items can be enabled in multiple projects, so a modal with a project select list is always needed, even in second pass
• After enabling, private item’s Enable button disappears/disables while public item’s Enable button remains visible for enabling in additional projects
• Non-maintainers always see the Enable button but get an empty state modal with a banner nudging them to contact their project maintainer, per Agent 2035’s proposal
• Group-level Automate page becomes read-only, showing items enabled by descendant projects with the disable button hidden

Enable Flow Table

Enabled from | Item scope | Enabling in | First pass | Second pass — Global (Explore)/Private/Managing project: modal with group/project pre-selected and immutable, user clicks enable → no modal, button does everything. Global (Explore)/Public/Any project user is maintainer of: modal with project select list, user selects project and clicks enable → same (modal still needed for project selection). Project namespace/Private/Current (managing) project: Enable button opens modal with project pre-selected and immutable → no modal, button enables directly and then hides/disables. Project namespace/Public/Current project or other project: Enable button opens modal with project select list, button remains visible after enabling → same (modal still needed), toast with link shown if enabled in a different project.

Key Behavioural Notes

Private items can only be enabled in the owner/managing project, so the target is always known — first pass uses a modal with the project pre-selected, second pass removes the modal entirely since there’s only one valid target. Public items can be enabled in multiple projects, so a modal with a project select list is always needed, even in second pass, since the user must choose which project(s) to enable in. After enabling a private item, the Enable button disappears/disables, since the item can only be enabled once. After enabling a public item, the Enable button remains visible so the user can enable it in additional projects. Non-maintainers always see the Enable button, but the modal shows an empty state with a banner nudging them to contact their project maintainer, per @Agent 2035’s proposal. The group-level Automate page becomes read-only, showing items enabled by descendant projects with the disable button hidden.