Granular Permission Based Data Access Control

via “row-level access control and user-specific data filtering”

No-code app builder from spreadsheets — AI-generated mobile and web apps.

Unique: Glide's row-level filtering is declarative and integrated into the data binding layer, meaning access control is defined once and automatically applied to all components that reference the data. This is more maintainable than UI-layer filtering (which can be bypassed) and doesn't require developers to manually add filters to each component.

vs others: More granular than Airtable's view-based sharing (which shares entire views, not individual rows) and simpler than custom code-based access control, though less flexible than database-native row-level security (RLS) in PostgreSQL or similar systems.

via “granular permission control and agent action authorization”

AI agent that generates production code from specs.

Unique: Implements granular permission control as first-class feature in agent configuration, enabling fine-grained authorization without requiring code changes. Permissions are enforced at runtime during agent execution.

vs others: Provides agent-specific authorization unlike GitHub (repo-level access control) or Slack (workspace-level permissions); similar to IAM systems but integrated into agent planning. Permission granularity and audit logging are undocumented.

via “role-based access control with granular permission enforcement”

AI platform for building internal business apps.

Unique: Enforces permissions at the server-side query layer before data is serialized, combined with attribute-based rules that evaluate user properties dynamically, ensuring that permission changes take effect immediately without requiring application redeployment

vs others: More granular than Airtable's sharing model because it supports field-level and record-level restrictions, and more flexible than Retool because it includes built-in ABAC evaluation rather than requiring custom middleware

via “role-based access control with field-level and record-level permissions”

NocoBase is an open-source AI + no-code platform for building business systems fast. Instead of generating everything from scratch, AI works on top of production-proven infrastructure and a WYSIWYG no-code interface, so you get both speed and reliability.

Unique: Combines role-based, field-level, and record-level permissions in a single system with visual configuration UI. Uses a declarative permission model where rules are stored as data and evaluated at query time, enabling dynamic permission changes without code deployment.

vs others: More granular than Airtable's shared bases because it supports field-level and record-level permissions, and more flexible than hard-coded role systems because permissions are configurable through UI without requiring code changes.

via “role-based access control with row-level data permissions”

AI低代码平台，支持「低代码 + 零代码」双模式：零代码 5 分钟搭建业务系统，低代码模式一键生成前后端代码。 内置AI 应用，支持AI聊天、知识库、流程编排、MCP与插件，支持各种模型。Skills能力实现：一句话画流程图、设计表单、生成系统。 引领 AI生成→在线配置→代码生成→手工合并的开发模式，解决Java项目80%的重复工作，快速提高效率，又不失灵活性。

Unique: Combines Spring Security RBAC with MyBatis-Plus row-level filtering for transparent data permission enforcement at the SQL layer, supporting both role-based and attribute-based access control

vs others: Enforces row-level security transparently at the database query level, whereas application-level filtering (post-query) is slower and error-prone

via “intelligent permission and access control with role-based sharing”

AI-powered universal search and assistant for work

via “access control and query permission enforcement”

Python-based AI SQL agent trained on your schema

via “fine-grained user-level access control and multi-tenant database switching”

Chat with SQL database, explore and visualize data

via “granular-access-control-management”

via “granular permission-based data access control”

via “permission-and-access-control”

via “attribute-based-access-control”

via “granular permission and access controls”

via “granular permission management”

via “granular-access-control”

via “row-level-access-control-enforcement”

via “role-based access control”

via “role-based data access control”

via “role-based access control and permissions”

via “fine-grained-access-control”