Skip to main content
News

Share Repository Documents in External Integrations ⭐

  • February 12, 2026
  • 7 replies
  • 88 views

Kelsey Gaag
Forum|alt.badge.img+16

Distribute your process documentation across your digital ecosystem with embedded repository documents! Repository documents can now be shared through a variety of Lucid integrations, allowing you to keep crucial documentation together and efficiently distribute sources of truth within the systems where you work. 

 

Embed repository documents in Confluence

This feature is only available to users with the Process Accelerator add-on.

To embed repositories, a user must be assigned as a process manager, repository owner, or process owner. When embedding, users with a Process Accelerator role can define the embedded document access level by choosing between comment or view-only permissions

Repository docuemnts can be embedded in the following third-party systems:  

Repository documents can be created in Lucidspark or Lucidchart. To embed your chosen document, make sure to select the app in which the repository was created.  

For more information, check out the Help Center articles linked above.

Comments

Astrid_G
Forum|alt.badge.img+9
  • February 12, 2026

Are there any plans to allow embedding within MS Word?


Kelsey Gaag
Forum|alt.badge.img+16
  • Author
  • Lucidite
  • February 18, 2026

Hi ​@Astrid_G
Thanks for the reply! As of right now there aren’t currently plans to add this capability. However, our PM over this team would love to hear more about your experience. Do you mind if I provide them with your email so they can learn more about your use case?


Astrid_G
Forum|alt.badge.img+9
  • February 18, 2026

Hi ​@Kelsey Gaag   I would be happy to participate.  I already met several people on the PA team last year when I did some beta testing before it went live.


Astrid_G
Forum|alt.badge.img+9
  • February 26, 2026

@Kelsey Gaag Any idea when they might be reaching out?  It just seems odd that repo docs can be embedded in Excel & Powerpoint and not Word.  We have Word as the basis for our Business Process Design docs, and the plan is to embed the Lucid doc with the associated flow diagram.  If we cant do that with diagrams that are published to a repo, it makes the PA somewhat pointless.  If you embed the non-repo version from a team folder, and then it gets published to the repo, will the link still work?


Astrid_G
Forum|alt.badge.img+9
  • March 3, 2026

@Kelsey Gaag Without the ability to generate a link for a doc in a repo for pasting into Word, it makes the repo system unusable for our company.  


Kelsey Gaag
Forum|alt.badge.img+16
  • Author
  • Lucidite
  • March 4, 2026

Hi Astrid, let me follow up with the PM to see when they will reach out!
 

If you embed the non-repo version from a team folder, and then it gets published to the repo, will the link still work?


That is a good question, since the document will change locations and repositories cannot be embedded in Word, I believe the document will no longer be embedded in the Word document. 


Astrid_G
Forum|alt.badge.img+9
  • March 4, 2026

@Kelsey Gaag Thank you.

I have been experimenting with the embedding process today, and with the LucidChart Add-In enabled within MS Word, it almost works.  The Repositories are available in the selection panel on the left and can be navigated.  Once you get to a file and select it, there’s a po-up saying that sharing permissions are needed to allow embedding.  I am the Process Owner of that doc and am the overall Process Accelerator admin so is it the message that is wrong?  or is it just a case of dealing with the permissions?
If embedding of repo docs is not supposed to be allowed within MS Word, then the Repositories section should not be visible, or should be greyed out so it can’t be selected.

 

Also, I have found an issue with embedding into either Excel or PowerPoint.  it works as long as you select “View Only”, but if you select the middle option to allow comments then the embed panel grays out and just hangs.  I will be submitting that as a product issue.