How to Configure ScyllaDB User Roles
You set up scylladb user roles by turning on role checks in your database config file. Next, you log in as a superuser to create accounts and assign table rules. Most teams start by making a few shared accounts for developers and apps. Over time, these shared roles gain too many rights across keyspaces. Broad roles let one bad query change or drop live production data. How scylladb user roles work in practice By default, a new database cluster lets anyone log in without a password. To fix thi
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up scylladb user roles by turning on role checks in your database config file. Next, you log in as a superuser to create accounts and assign table rules. Most teams start by making a few shared accounts for developers and apps. Over time, these shared roles gain too many rights across keyspaces. Broad roles let one bad query change or drop live production data.
How scylladb user roles work in practice
By default, a new database cluster lets anyone log in without a password. To fix this, admins change the login settings in the node config files. You must also set the role manager to check permissions on every request. After you change the files, you restart each node in the cluster. The database stores all account data in an internal system keyspace. You should raise the replication factor of this system keyspace right away. If a node goes down, higher replication keeps your login system working.
Once the cluster restarts, you log in with the default admin account. Your first step is to create a new superuser role with a strong password. Then you remove or lock the default admin account to keep the cluster safe. In this database, roles replace the older concept of simple users. A role can represent a single person, a backend app, or a whole team. Some roles have the login flag turned on so people can sign in. Other roles act as groups that hold permissions without allowing direct logins.
Admins grant permissions to these group roles on specific keyspaces, tables, or functions. You can allow a role to read rows, write data, or alter tables. Then you grant the group role to individual developer or app roles. When a user logs in, their account inherits all rules from the assigned groups. This setup keeps you from assigning table rules to every person by hand.
What native role setup solves and where it falls short
Native roles give your team a clear way to divide database duties. You can keep read-only analysts from changing records in core tables. You can also stop an app in one keyspace from reading another keyspace. Storing roles inside the cluster means every node shares the same rule list.
Still, native database roles have clear limits during daily operations. A role decides who can log in and which tables they can touch. It does not inspect what individual queries do while a session is active. If an engineer needs to fix one row, they need write rights. Those same write rights let them update or delete every row by mistake. Native roles also remain active twenty-four hours a day until someone revokes them. Teams often forget to remove temporary write rights after an incident ends.
User Provisioning (SCIM) + Lambda Execution Roles: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Database roles cannot mask sensitive fields inside a table on their own. If a role can read a customer table, it returns the whole row. The query result includes raw emails, phone numbers, and card numbers. Auditing is also hard when several people share one role for support tasks. The database logs show the shared role name instead of the real person. Finally, rotating passwords across many clusters takes hours of manual work each month.
Best practices for managing database permissions
Start by creating separate group roles for read, write, and schema tasks. Never give superuser rights to apps or daily developer accounts. Assign login rights only to roles that belong to one specific person or service. Review your system keyspace tables often to find unused accounts and extra permissions. Keep production keyspaces locked down so humans only hold read rights by default. When someone needs to run a data fix, check the query before it runs.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.
First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
How are roles different from users in ScyllaDB?
Roles are the modern way to manage both accounts and permission groups. A role can hold login rights or act as a group you grant to others.
Why should I change the system auth keyspace replication?
The database keeps all role and password records inside that internal keyspace. Raising its replication ensures people can still log in if a node fails.
Can native roles hide sensitive columns like emails or card numbers?
No, native permissions work at the keyspace or table level during a query. To rewrite emails or card numbers in results, you need external data masking.
Related guides
In this post