Summary: We'd like the ability to grant teammates access to create and edit Fin Procedures without also giving them visibility into or access to Workflows, automation settings and other sensitive operational areas of our Intercom workspace.
Current Behavior: Today, Procedures live within the Fin AI Agent tab, which is accessed via the "Can view Fin and Automation settings" permission. This same permission also exposes Workflows and Simple Automations. There is no way to grant procedure-building access in isolation, any teammate who can work on procedures can also see workflows.
To prevent teammates from editing workflows, we can withhold the "Can manage Automation settings and inbound Workflows" and "Can manage outbound Workflows" permissions, but those teammates will still have full visibility into workflow configurations, which is not ideal from an access control and operational security standpoint.
Requested Change: Introduce a dedicated permission (e.g., "Can manage Fin Procedures") that:
- Allows teammates to create, edit, and manage Fin Procedures
- Does not expose Workflows, Simple Automations, other automation settings or operationally sensitive areas of the workspace
- Can be granted independently of any workflow-related or data / security related permissions
Use Case: We want to involve subject matter experts and content contributors in building and refining Fin Procedures, teammates who understand our processes deeply but should not have access to the broader automation and workflow configuration of our workspace. Today, there's no clean way to enable this without overexposing sensitive operational settings.
Desired Outcome:A permission model that lets us confidently delegate procedure authorship to a wider group of teammates, with clear boundaries that protect workflow integrity.