Hi all,
I created a flow in GTI that sends the results of a prompt to several team members via email each day. The issue is that recipients are unable to view the prompt when they click the GTI link included in the email.
I've already verified everyone's permissions and haven't found any issues there. Has anyone else encountered this problem or found a solution?
Best answer by aymanabdelaziz
Hi ,
Thank you for reaching out and sharing this question with the community!
First, great job on double-checking everyone's permissions right away, that is usually the best place to start.
In this particular case, however, the behavior you are seeing is actually due to a current platform limitation rather than any configuration error on your side.
While GTI users can easily share manual, one-off Agentic conversational sessions, the ability to collaborate on and share automated Flows is still on our product roadmap and not yet natively supported.
When a scheduled Flow executes a prompt and dispatches an automated email report, that execution remains strictly tied to the Flow creator's account. This means your team members will successfully receive the structured email digest, but they won't be able to access the underlying session link inside the GTI portal.
While our engineering team works on bringing native Flow collaboration to the platform, here are three best practices we recommend to optimize your team's workflow:
1. Optimize the Email Output with Prompt Engineering: Since your team members are relying strictly on the email body, you can use advanced prompt engineering to make sure the delivered report is completely self-contained. According to GTI best practices, try updating your prompt to include rigid Output Format instructions (e.g., specifying length, tables, formatting, order, and dedicated sections) and clear Context guidelines. This ensures the email itself provides all the depth they need without them ever having to click into the platform.
2. Use Manual Session Sharing for Deep Dives: If a team member receives a scheduled report and needs to investigate that specific run further, the Flow creator can manually open the execution session from their own history and click the Share button. This will generate a shareable link allowing other users to view and fork the conversation to explore different analysis paths.
3. Individual Flow Setup: Until collaborative Flows are officially released, any team members who need to independently manage, edit, or interact with these automated queries will need to recreate the Flow under their own respective accounts.
We are actively working on expanding our collaboration features in future GTI updates, so stay tuned!
+2Hi ,
Thank you for reaching out and sharing this question with the community!
First, great job on double-checking everyone's permissions right away, that is usually the best place to start.
In this particular case, however, the behavior you are seeing is actually due to a current platform limitation rather than any configuration error on your side.
While GTI users can easily share manual, one-off Agentic conversational sessions, the ability to collaborate on and share automated Flows is still on our product roadmap and not yet natively supported.
When a scheduled Flow executes a prompt and dispatches an automated email report, that execution remains strictly tied to the Flow creator's account. This means your team members will successfully receive the structured email digest, but they won't be able to access the underlying session link inside the GTI portal.
While our engineering team works on bringing native Flow collaboration to the platform, here are three best practices we recommend to optimize your team's workflow:
1. Optimize the Email Output with Prompt Engineering: Since your team members are relying strictly on the email body, you can use advanced prompt engineering to make sure the delivered report is completely self-contained. According to GTI best practices, try updating your prompt to include rigid Output Format instructions (e.g., specifying length, tables, formatting, order, and dedicated sections) and clear Context guidelines. This ensures the email itself provides all the depth they need without them ever having to click into the platform.
2. Use Manual Session Sharing for Deep Dives: If a team member receives a scheduled report and needs to investigate that specific run further, the Flow creator can manually open the execution session from their own history and click the Share button. This will generate a shareable link allowing other users to view and fork the conversation to explore different analysis paths.
3. Individual Flow Setup: Until collaborative Flows are officially released, any team members who need to independently manage, edit, or interact with these automated queries will need to recreate the Flow under their own respective accounts.
We are actively working on expanding our collaboration features in future GTI updates, so stay tuned!
Thanks!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
