How to Configure Couchbase Create User

Published
Length
3 min read

Luis Felipe Dias

All posts

To run a couchbase create user action, you add an account and assign a role. You can do this in the web console, the command tool, or the REST interface. Most teams start by making one shared account for their whole group. They often grant wide cluster roles so everyone can finish their work fast. Over time, these broad roles give too many people full read and write power. How the couchbase create user workflow works First, an admin picks where the new account will live and check in. Local ac

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.

To run a couchbase create user action, you add an account and assign a role. You can do this in the web console, the command tool, or the REST interface. Most teams start by making one shared account for their whole group. They often grant wide cluster roles so everyone can finish their work fast. Over time, these broad roles give too many people full read and write power.

How the couchbase create user workflow works

First, an admin picks where the new account will live and check in. Local accounts store their name and secret inside the database cluster itself. External accounts link to an outside directory that your company already runs. Next, the admin picks one or more built-in roles for that person. A role can apply to the whole cluster or to one specific bucket. You can even narrow a role down to a single scope or collection. When a person logs in, the cluster checks their name and secret. Then it loads the list of roles tied to that specific account. You can also place accounts into groups to make role updates much faster. When someone joins a group, they get every role that the group holds. If they leave the team, you just remove them from that group.

Why you should scope roles down

Giving everyone a full admin role is a common mistake in busy teams. It feels fast at first, but it creates huge risks for your data. An engineer might run a bad query that wipes out a live collection. A test script might read real customer records by mistake during a check. Scoping roles down to one bucket or collection stops most of these mistakes. App accounts should only get read and write rights for their own data. Human accounts should get read-only roles when they look into live bugs. You should separate cluster admin tasks from daily data read tasks right away. Keeping roles small makes audits much simpler for your security team later on.

What native roles solve and what they leave open

Native database roles do a great job of locking down cluster settings. They stop random users from dropping buckets or adding new nodes to the cluster. They also let you split data rights across different buckets and scopes. Still, native roles only check who logs in and which bucket they touch. They cannot inspect individual queries or commands while those requests run in flight. Once a user has read rights on a collection, they get every field. If a document holds emails, phone numbers, or card numbers, the query returns them. Native roles also force admins to manage static secrets for every local account. People often share these secrets in chat rooms or save them on laptops. When someone leaves the company, rotating shared secrets can break running apps. Finally, basic role checks do not ask a teammate to approve risky updates.

User Provisioning (SCIM) + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

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 local and external users in Couchbase?

Local users store their login name and secret right inside the database cluster. External users verify their identity through an outside directory service that your team manages. Both user types still get their data roles from the database cluster itself.

Can I limit a user role to a single bucket or collection?

Yes, many data roles let you pick a target bucket, scope, and collection. This setup keeps a user or app from reading data in other areas. Always pick the smallest scope that still lets the person do their job.

Why do shared database accounts cause problems during security audits?

When five engineers share one login name, the logs show one account. You cannot tell which person ran a specific query or deleted a record. Giving each person their own identity fixes this gap in your audit logs.

The query runs. The emails stay hidden.