Invision is a popular tool for visual designers and UX designers, but it is usually a pain to transfer the information over to Jira. With Invision for Jira that becomes less problematic since you can embed an inline prototype directly into a Jira issue that also include the inspect function that makes life easier for the developers.
While this is very nice, it really is just a fancy way to link people to Invision because the links will take you to Invision and you get the same issue with making sure everyone have a login and understand the way Invision works. This does not solve the actual problem to bring in the information the designers need into the documentation, it just add a more convenient way to direct the users to Invision.
Clicking the Preview button will open your prototype in InVision. If you click the Comment button, your prototype will open in a new tab or window in Comment Mode. Click the Inspect button to open your prototype in Inspect Mode in InVision. Clicking on the thumbnail preview will open the share link in a new browser tab so that it is possible for a user that does not have access to InVision to be able to view the prototype.
So this leaves the designs in Invision, which is not a good place to keep designs once they are agreed upon since you need to ensure the designs are not continuously improved as that cause issues with requirements. This can be solved by transferring projects to a another, controlled Invision instance, but that is messy and prone to confusion and mistakes.
What I would like to have is a way to embed this directly into Confluence where it can be version handled and controlled from a requirements perspective. The concept is amazing, but the solution right now is not enough for a good way to bring in design in a controlled way as a requirement into Jira unfortunately.