How to Configure ScyllaDB Create User
You run the scylladb create user workflow by setting up a database role with login rights. Modern database versions use roles instead of the older user command to manage accounts. Many engineering teams start by sharing one admin account across several apps and developers. When permissions are too broad, a single bad query can wipe out whole tables. Setting up separate roles for each person and service is the first step toward safety. How the scylladb create user workflow operates Before you
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 run the scylladb create user workflow by setting up a database role with login rights. Modern database versions use roles instead of the older user command to manage accounts. Many engineering teams start by sharing one admin account across several apps and developers. When permissions are too broad, a single bad query can wipe out whole tables. Setting up separate roles for each person and service is the first step toward safety.
How the scylladb create user workflow operates
Before you add any new accounts, you must turn on password checks in the cluster settings. By default, a fresh cluster often lets anyone log in without a password check. An admin updates the cluster settings file on every node and restarts the service. After the restart, you log in with the default admin account to set up new roles.
Inside the database shell, the role command replaces the legacy scylladb create user statement. Both commands still work, but role commands let you group permissions and assign them to people. When you make a role for a developer, you turn on the login option and set a password. When you make a role for a team group, you leave the login option turned off. You then grant the team role to the individual developer role so permissions stay neat.
Next, you must replace the default admin account as soon as your own admin role works. Every attacker knows the default login name and password for a fresh database cluster. You make a new superuser role, log in with it, and delete the default account. Finally, you grant specific read or write rights on keyspaces and tables to standard roles. The database stores these account records inside an internal system keyspace that copies across nodes.
What native roles solve and what they leave open
Native database roles do a great job of deciding who can log into the cluster. They also set clear boundaries on which keyspaces or tables a given role can touch. If a reporting app only needs read rights on one table, roles enforce that rule. This setup stops unauthorized apps from dropping tables or altering the cluster schema.
Still, static database roles only check permissions at the table or keyspace level. Once a developer logs in with a valid role, the database trusts every allowed query. A role with read rights on a customer table can pull every row at once by default. Native roles do not rewrite sensitive fields like emails, phone numbers, or card numbers in results. They also require you to hand out static passwords that sit in local files for months.
User Provisioning (SCIM) + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Also, managing human accounts across dozens of database clusters takes a lot of manual work. When an engineer leaves the team, someone must log into each cluster and drop their role. If an admin forgets one cluster, that old password stays active and open to abuse. Native roles alone cannot tie every live query back to a corporate identity provider.
Managing permissions for humans and apps at scale
To keep clusters safe, teams should separate app accounts from human fixing accounts. Apps need steady roles with tight read and write rights on specific keyspaces. Humans rarely need full access all day, even when they fix a live production bug. Giving developers permanent superuser roles just in case an outage happens creates huge risk. Instead, teams look for ways to check every query in flight and mask sensitive fields.
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
What is the difference between a user and a role in ScyllaDB?
A user is an older database concept that only represents a single login account. A role is a newer, flexible object that can hold permissions, login rights, and other roles.
Why can anyone log in after I run scylladb create user?
The cluster ignores user accounts until you turn on the password check setting on every node. You must update the node settings file and restart the cluster to enforce passwords.
How should we handle the default superuser account?
You should create a new role with superuser rights and log in with that new account. Once you confirm the new account works, delete the default account right away to block attackers.
Related guides
In this post