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
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Logging is here!
Logging is now available for all Flare users! Send any log from your app to Flare and use our polished interface to filter and search your logs in real-time.
Jimi
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
