Skip to main content

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


Show first post

80 replies

Would like to see the options on this


  • 2 replies
  • January 15, 2024

Any updates here? The message still appears when trying to forward the prototype to external parties…


Anthony_Ina1

I’m still seeing this message as of writing.


dvaliao
Figmate
  • Community Support
  • 4664 replies
  • February 23, 2024

Hey All, thanks for your feedback!

We’ve updated this topic to a feature request for users without a Figma account or are not logged in. As mentioned above, we’ve only removed interstitials for external links in Figma and FigJam when logged in.


  • 1 reply
  • February 24, 2024

During most user testing, users are not logged in and are using a browser.

If the prototype creator’s information is visible, those publishing the work should be responsible for all links. I am not sure there are significant security concerns.

The notification could be changed to a toast message, or at least, this page should not display such small text on mobile browsers like Safari (this page wasn’t responsive).

Sincerely hope attention can be given to this issue!
Much appreciated, Figma team!


Dan_Lutger

Much needed! Thank you!


This is still an issue. I don’t think Figma cares about their users and just wants to drain money from us.

They only fixed it for users who are logged into Figma, obviously they want as many users on a paid plan as possible. It is unlikely when doing user testing that all participants will have Figma accounts and sharing my account with them is arguably more unsafe. It is just ridiculous as other things like Invision allow this.


  • 1 reply
  • July 2, 2024

Surprised nothing has been done about this because it fundamentally breaks Figma as a tool for usability testing.

As has already been mentioned participants in usability testing are not going to be logged in to Figma (or even have an account), so they are always going to see this interstitial when visiting external links.

At least make the warning responsive so the text is legible? Currently we are having to coach participants to navigate past it in the middle of a session.


I do not think they care. Maybe will look into using Penpot.


  • 1 reply
  • August 13, 2024

Logged-in or Logged-out accounts do not matter. There is still an issue on Desktop Figma even for the logged-in account. Figma Prototype and Figma Slides presentation.

It’s a terrible flow-breaking decision — make it a preselection, dialog question at the start, or anything else.


dvaliao
Figmate
  • Community Support
  • 4664 replies
  • August 13, 2024

Hey @Arsen, thanks for following up!

We just tested it, and it’s still working as expected when logged in with a Figma account on both the browser and desktop app using a macOS device and Chrome browser. What are you using?

As we see it, the interstitial will show once the 1st time upon leaving to go to the external link. And as long as you check the option to not show again, it shouldn’t show itself again going forward.

As a workaround, for those still seeing this message even when logged in, check that your browser version is supported and up to date. And, if you’re using the prototype action [Open link], be sure to check [Open in new tab] option.

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.


tylor.andrews

I think the 44 users in this thread and 8k+ views of people looking up this exact issue should count more than expecting people to vote here… I’ve been using Figma the past month to create a better experience for internal users accessing our resources at my fortune 500 and I’m getting the same friction and complaints as everyone here. I’m shocked this has been a known and unattended issue for years now. Unfortunately I now have a week to rebuild the experience native in sharepoint and will never use Figma again. Thanks for your “support”…


Deba
  • 1 reply
  • October 15, 2024

Please, can something be done about these interstitials? They’re terrible, and they make Figma prototypes almost unusable, considering that the general populace does not have Figma accounts. @dvaliao


Yaroslav_Poliakov

We planned to use a prototype for MVP of a new feature, but then discovered existence of this warning screen and prototype become useless. You cannot show this to the users, it just breaks a flow 🤷


Danny14
  • 1 reply
  • October 29, 2024

Same here - we can’t use Figma prototypes for usability tests that link out to the live site. It breaks the flow and confuses the user (who are very rarely Figma users). Anyone got recommendations for a prototyping tool that doesn’t do this…?


Morgan_Gold
  • New Member
  • 2 replies
  • December 5, 2024

Please remove this ‘feature’


Iago_Sousa
  • New Member
  • 3 replies
  • January 20, 2025

O problema é que esse recurso atrapalha a experiência do usuário durante o teste, e vocês ficam batendo na mesma tecla de que a unica solução é remover esse recurso no navegador mobile, enquanto isso a visualização dessa tela não tem nem responsividade e fica dessa forma minusculo, ela não atrapalha o usuário, ela trava o usuário pois ele pensa que é um erro, 

poderiam pelo menos fazer com que essa tela seja responsiva para que qualquer ser humano consiga ler o que está escrito?

Além disso o texto é por padrão em ingles, eu acho que vocês tem um lobby com o Maze, só pode, 

Moro no Brazil e se eu for fazer um unico teste de usabilidade com o Maze gasto 99 dolares, o que corresponde a 600 na moeda brasileira (metade de um salario minimo)

por favor, façam o minimo, que é ter responsividade nessa tela!


Iago_Sousa
  • New Member
  • 3 replies
  • January 20, 2025

Ou pelo menos adotem excessões para redirecionamentos para google forms / typeform, uma discussão enorme para algo tão bobo...


Morgan_Gold
  • New Member
  • 2 replies
  • January 23, 2025

How is this so hard to get rid of?


Vanez_Polyansky

Shame on you Figma team. Such an easy issue to fix but you just obviously don’t care. 


Ancu
  • New Member
  • 1 reply
  • 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
  • 1 reply
  • February 18, 2025

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


Jaz Wilkinson
  • New Participant
  • 6 replies
  • 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
  • 6 replies
  • 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

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?


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings