Flare already contains stack traces, request data, and environment details for your application's errors. That's sensitive information — and it makes sense to protect access to it.
That's why we've added the ability for team admins to require two-factor authentication for all team members. Once enabled, every member of your team will need to set up 2FA before they can access any
projects or errors.
You'll find the new toggle in your team's Security settings. When you enable the requirement, a confirmation modal makes sure you're intentional about it. And of course, you'll need to have 2FA enabled on
your own account first before you can require it from others.
Team members who haven't set up 2FA yet will be redirected to their security settings with a clear message explaining what's needed. They won't be able to access anything in the team until they've
completed the setup.
If you're working with a larger team or handling production error data, this is an easy way to add an extra layer of protection to your Flare account.
Continue reading
A minimal "Last used" login option indicator with Alpine.js
Flare's login page now remembers which sign-in option you used last time. Built on Alpine's $persist plugin and just about 25 lines of code.
Alex
How Flare handles Livewire v4's single file components
Single file components are a great addition to Livewire v4, but their compiled output makes debugging harder. Here's how we taught Flare to map hashed file paths and line numbers back to your actual source files.
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates