Authorisation module for the Play! framework
Java Other
Latest commit 8a3a3f6 Jan 9, 2015 @schaloner Update README.textile
Clarified this is for Play 1
Failed to load latest commit information.
app Fixed incorrect logging message Aug 23, 2012
documentation/manual document updated for deadbolt.externalizedRestriction tag Apr 11, 2012
public/stylesheets Restricted resources can have multiple names. Initial implementation … Apr 1, 2011
samples-and-tests fixed interaction between different restriction categories May 29, 2012
src initial import Dec 25, 2010
LICENSE.txt updated license info Dec 25, 2010
README.textile Update README.textile Jan 9, 2015
build.xml initial import Dec 25, 2010 initial import Dec 25, 2010



Deadbolt is an authorisation mechanism for the Play 1 framework for defining access rights to certain controller methods or parts of a view using a simple AND/OR/NOT syntax. It is based on the original Secure module that comes with the Play! framework.

Note that Deadbolt doesn’t provide authentication! You can still use the existing Secure module alongside Deadbolt to provide authentication, and in cases where authentication is handled outside your app you can just hook up the authorisation mechanism to whatever auth system is used.


  • Define access using AND, OR and NOT combinations
  • Define access at the class, method or view level
  • Define permissions at the database level, allowing you change them instantly without redeploying
  • Define restricted resources at the class, method or view level and control access to them on an artibrarily fine-grained level. You can also drop back to other restrictions to allow specific and general cases in the same combination.
  • Combine all of the above to get the best fit for your application