Decide who should be able to read or continue the conversations an automation creates. This is separate from deciding which connected account the automation uses to perform its work.
Choose the audience
Review Chat access in the automation setup. Depending on the configuration, you can keep output private, share it with the project, or choose specific people from that project.
Private output can be opened only by the automation owner. Project access follows the project's current membership. Read the displayed permission: a shared run may be read-only or may allow members to continue its conversation.
Sharing an automation requires a project, and selected people must belong to that project. If an agent is selected for project work, it must be attached to the project.
Check who can manage it
The automation owner or a project manager can edit the automation. Being able to read output is not the same as being allowed to change its instructions or trigger.
Check data access
Review the input accounts and the information included in the result. Sharing output does not share the connected account's credentials, but the output itself may contain information retrieved from that account.
When membership or account access changes, review the automation's audience and connections before its next run. Test visibility from an intended recipient's account.
See project members, sharing, and connector permissions.