Skip to main content
Doug_Wickham
Active Member
March 26, 2021

Remove Leaving Figma External Link Warning for anyone without an account/not logged in

  • March 26, 2021
  • 84 replies
  • 10417 views

Im creating a prototype and would like to link to live pages on our site without having the User in the test have to see the “Leaving Figma Warning” page. My concern is that it takes it breaks the illusion of an actual experience.

Is there a way remove this middle page from the experience?

84 replies

Ancu
New Member
February 18, 2025

Hello!

A few months ago, I developed some prototypes for SharePoint and integrated them as embedded components. Everything was functioning well until recently, when a “Leaving Figma…” message started appearing.

 

Figma team, please consider that many of us create prototypes for end users who do not have Figma accounts. It is crucial to provide a product that ensures a great customer experience.

Please let us know if this issue can be resolved, or if we should explore alternative solutions outside of Figma.

Thank you!

Ancuta

 

Beth Stojkov
New Member
February 18, 2025

+1, this feature request is critical for user testing ​@dvaliao 

Jaz Wilkinson
New Participant
February 24, 2025

This ‘feature’ is an absolutely disaster. We basically cannot use Figma for our mobile prototypes because of it - why why why have you done this @figma?

PLEASE at least make it a setting where we can make the decision that we don’t need this security feature for our prototypes.

(It is not acceptable for user research participants to have to be logged in to not see this interstitial - again, why are you making things so hard for us to do good user testing?)

Jaz Wilkinson
New Participant
February 24, 2025

This is a MAJOR problem. It is totally unrealistic for every random one-time user research participant to have to have a Figma account and be logged in not to see this step. SO embarrassing to not be able to do user testing in Figma and have to use another tool instead. Figma does not care about or understand user research and never has.

Guillaume_Coquoz
New Member
February 25, 2025

As already stated above, this is on our team’s radar for improvement. But to be completely transparent, with only 17 votes from the community, my team here on the forum cannot make a substantial case that this is truly impacting users to have this prioritized with urgency.

 

 ​@dvaliao while understanding that you are not responsible for it, the “# of votes” prioritization model can’t work for all topics and features. 

You (Figma) have to take into consideration the fact that there is no alternative here! 

We (your clients) are stuck with a feature that prevent Figma to work properly. What can be more of an urgency?

Jaz Wilkinson
New Participant
February 27, 2025

Indeed, this problem makes it impossible to use Figma for prototyping, so I am now using another product (UXPin) instead. How ridiculous. ​@Guillaume_Coquoz can you give us some insight as to why this ‘feature’ even exists in the first place? I will eat my hat if you tell me that more people asked for it (or anyone asked for it at all) than have complained about it. Really bad, nonsensicle product decision.

Jaz Wilkinson
New Participant
February 27, 2025

​@Guillaume_Coquoz If you were to combine all the complaints in different threads, there would be more - e.g.

 

Guillaume_Coquoz
New Member
February 27, 2025

​@Jaz Wilkinson I’m not working for Figma so I can’t tell you exactly why the feature exist but I guess it have something to do with pishing prevention and security measures. Which is a real use case to be solved, don’t get me wrong.

 

​@dvaliao Jaz’s comments shows exactly what I’m trying to state (and there is many other similar comments); this feature breaks your product and encourage your paying customers to go look for other products to do the job Figma is supposed to do. That’s probably something you don’t want to happen. No matter how many Likes on a customer forum topic.

Jaz Wilkinson
New Participant
February 27, 2025

I see ​@Guillaume_Coquoz thanks. I did assume it was a security feature at first, but that fact that it goes away if users are logged into Figma suggest that it is not essential. I really don’t want to go to the place to think that it is a dark UX pattern to force you to have to give every user research participant you work with a Figma login to be able to run a sensible user test, but I cannot see any other reason why this is like this.

IMHO Figma don’t have a great understanding or sense of priority for the user testing process - something that all designers should be doing, but in my experience, most don’t do enough of. Partly, because Figma makes it so hard.

It is absolutely not practical to give a Figma account to every user research participant, that are random people you will engage with once and never see again. Just blows my mind that someone thought that was a sensible solution.

Dan Satterfield
New Member
March 14, 2025

Using external links without a warning screen was the major reason I switched to Figma. When I was testing (while signed-in) external links worked like a charm. Now realizing my error in not digging deeper into the weeds is unfortunate and deflating 🎈.


​@dvaliao is liking 👍the original post considered upvoting? If not, please let me know how to cast a vote to the urgency of this major pain point.

To all who learned this long before me, thank you for sharing.
For all those after me please upvote, upvote, upvote 🚀📈🎉.

Hopefully 😁 this will happen before I am fully grey 👴🏻.