Dear Wiki user, You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification. The "PerDocumentAuthorization" page has been changed by jchrisa. The comment on this change is: note about per-doc authorization. -------------------------------------------------- <> = Introduction = CouchDB has a good HTTP API which encourages you to put your client applications in direct contact with your database. However, most dynamic systems require some kind of authentication and authorization. Per database there is the possibility of using [[Authentication and Authorization]]. This wiki page tries to summarize the possible solutions to using per document authentication and authorization. + + '''Note:''' CouchDB has not be designed to support per-document read-control, and such a feature is not on the Roadmap. If you are reading this page, you should probably start thinking about using a database-per-security-group approach. In this model you create a database for a project, and grant only a certain set of users access to read and write to it. Filtered replication can be used to create subsets of a larger database when fine-grained control is needed. '''The problem:''' For a given user, allow only specific access to a given document in the database.