---
title: "Announcing version history support for Cloud Firestore Security Rules"
description: "Announcing version history support for Cloud Firestore Security Rules"
published: "2018-04-09"
last_updated: "2018-04-09"
authors:
  - "Rachel Myers (Developer Programs Engineer)"
categories:
  - "Firestore"
  - "Security Rules"
  - "Launch"
canonical_url: "https://firebase.blog/posts/2018/04/firestore-rules-management"
---

# Announcing version history support for Cloud Firestore Security Rules

*Published April 9, 2018 by Rachel Myers (Developer Programs Engineer)*

---
![image2](https://firebasestorage.googleapis.com/v0/b/first-class-blog.appspot.com/o/blog-assets%2F2018%2F04%2Ffirestore-rules-management%2Foptimized%2Fimage2.jpg?alt=media)

The Firebase console gives you the power to make changes to your Cloud Firestore Security Rules directly from your browser! Unfortunately, that also means your team has the ability to _break_ your security rules directly from your browser, maybe without remembering exactly what they changed. Well fear no more; Firebase has your back!

Recently, we added Version History to Cloud Firestore Security Rules. For any Cloud Firestore project, you can now browse all previously published versions of Rules, view the differences between the previous and current versions, and edit the current version -- either to a complete rollback to an earlier version or to a mix of rules.

![image2](https://firebasestorage.googleapis.com/v0/b/first-class-blog.appspot.com/o/blog-assets%2F2018%2F04%2Ffirestore-rules-management%2Foptimized%2Fimage2.jpg?alt=media)

Now, when your team introduces a bad security rule, it's a snap to find out what the previous working version was and get back to it.

To start using version history for Security Rules, simply [navigate to the Rules tab of Cloud Firestore](http://console.firebase.google.com/project/_/database/firestore/rules), and start browsing your version history in the left-hand column. From any older version, you can click "Compare to Latest" to view the diff and edit the latest version.

![image1](https://firebasestorage.googleapis.com/v0/b/first-class-blog.appspot.com/o/blog-assets%2F2018%2F04%2Ffirestore-rules-management%2Foptimized%2Fimage1.jpg?alt=media)

Every deploy that includes Rules is considered a new version; you'll see unchanged versions if you've deployed unchanged rules several times from the command line. To avoid that, you can call `deploy --only` from the Firebase CLI to deploy only the things you've changed. For example, I often make edits to my project's Cloud Functions without changing anything else, so I end up running `firebase deploy --only functions` from the command-line tool to make sure only the changes to my Cloud Functions get submitted.

Reach out to us via Twitter [@Firebase](https://twitter.com/firebase) or via our other [support channels](https://firebase.google.com/support/) to let us know what you think! We're looking forward to adding this to other Firebase features, and would like to get your feedback before we do.