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
Bringing Flare back to Laravel 10 and PHP 8.1
Flare now supports Laravel 10 and PHP 8.1 again, so older apps get performance monitoring and logs too. Here’s how we did it.
Ruben
Your Laravel routes can carry metadata now, and Flare shows it
Laravel added a new way to attach metadata to routes, and Flare now automatically shows it on errors and traces
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
