Skip to main content
Idea

Option to allow non-repo or process owners to embed repository documents externally

  • March 5, 2026
  • 1 reply
  • 9 views

Astrid_G
Forum|alt.badge.img+9

If someone working on a process flow diagram has submitted the approval request, which is confirmed and they then publish the document, but they are not the process owner they are not currently allowed to them embed that published document into another application. ie its normal within our org that the team lead or manager would be the process owner, and the individual contributors (licensed user) are building the diagrams and requesting the approval.

This seems un-necessarily limiting, and would make repo/process owners a bottleneck when it comes to getting repo docs embedded and then shareable.  

Given the inability to generate a shareable link directly to the repo doc, embedding into another application seems to be the only way to refer to and share the repo content easily.  otherwise each person wanting to see the published content has to launch Lucid and go and find it manually within the repos.  This is not a sustainable/effective way of sharing published content across the enterprise.

Comments

Leianne C
Forum|alt.badge.img+15
  • Lucid support team
  • March 19, 2026

 Hi ​@Astrid_G, thank you for posting in the community and apologies for the delayed response. I’m happy to share more information about this. Repository documents can only be embedded by the repository owner, process owner, or repository manager due to governance / security reasons. Since embedded documents are viewable to all users, limiting this permission to owners can help make sure the content is embedded to the right context. 

That said, I understand how this may not be suitable for all use-cases and have shared this feedback with our development team for consideration. If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within this thread. I’ve also converted this post to an idea so that it’s visible to others within the Product Feedback section of the community - from here, they can upvote it and add details of their own.

Finally, for more information on how Lucid manages feedback via this community, take a look at this post:

Thank you for sharing your feedback in the community. Please let us know if you have any questions.