<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permissions on Kuldeep Pisda</title><link>https://kdpisda.in/tag/permissions/</link><description>Recent content in Permissions on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 14 Mar 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/permissions/index.xml" rel="self" type="application/rss+xml"/><item><title>Permissions as Data: The ERP the Org Rewires Without an Engineer</title><link>https://kdpisda.in/erp-dynamic-permissions-with-django-groups/</link><pubDate>Sat, 14 Mar 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/erp-dynamic-permissions-with-django-groups/</guid><description>&lt;p&gt;The Ambarsthan booking engine from the last chapter put its foot down in exactly one place on purpose: the correctness of two people grabbing the same slot lives in the database — row locks, an exclusion constraint, the right isolation level — not in hopeful application code. Same Django backend, a very different neighbour app riding on it, and this time the hard part is not concurrency. It is change.&lt;/p&gt;</description></item></channel></rss>