Radius Column-Level Access

A query runs. The data moves. But not every column should be seen by every eye.

Radius column-level access gives you the control to decide exactly which table columns are visible, down to the single field. It enforces granular permissions at the database layer, so sensitive data like personal identifiers, financial numbers, or internal metrics never leave their secure boundary.

This is more than row-level filtering. With Radius, column-level access means each user, role, or service can query only the fields they are authorized to view. The rest are locked—unreadable, unwritable—while the query still runs at full speed. Policies bind directly to column definitions, ensuring security remains consistent even if query shapes change.

Implementation is straight from source control. Define access rules in a configuration file or within your schema, deploy them with your application, and let Radius apply them at runtime. No extra middleware, no brittle query rewrites. This approach minimizes attack surface and prevents accidental leaks during development or debugging.

Radius integrates with your existing identity and role system. Map roles to column groups, align them with compliance requirements, and keep your audit trail clean. Because restrictions happen in the database engine itself, they are enforceable across every client—CLI tools, APIs, reporting dashboards—without duplicate logic.

The result is a lean, predictable security posture. You won’t rely on application code to filter private data. You gain a single source of truth for access control that lives in the same place as your schema—a setup that’s easier to review, maintain, and trust.

See how Radius column-level access works in practice. Visit hoop.dev and deploy a live instance in minutes.