Why read-only access alone is not enough to secure an AI-powered HR assistant

Adding an AI assistant to an HR platform introduces permission challenges that go beyond simply restricting database writes. A read-only connection does not control which rows or columns a user can see, meaning even aggregate queries can inadvertently expose sensitive data like individual salaries. Effective access control must account for both the type of operation and its data scope, enforced at the application and data-access layer rather than through prompt instructions alone. The article uses WorkBento, a self-hosted Python HR platform, to illustrate how role-based permission matrices and workspace-scoped queries can address these risks. Developers are advised to validate access boundaries using sample accounts and test scenarios before deploying any AI assistant against real employee data.