How to Configure Greenplum Create User
You run a greenplum create user task by adding a new role with login rights. The coordinator node saves this role in the system catalog and shares it across segments. Database teams often create shared group roles to speed up daily setup for analysts. Then they add people to those groups as new projects start. Over time, these shared roles collect broad read and write rights across many schemas. When permissions grow too wide, one mistake can break tables or expose private rows. How the greenp
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 a greenplum create user task by adding a new role with login rights. The coordinator node saves this role in the system catalog and shares it across segments. Database teams often create shared group roles to speed up daily setup for analysts. Then they add people to those groups as new projects start. Over time, these shared roles collect broad read and write rights across many schemas. When permissions grow too wide, one mistake can break tables or expose private rows.
How the greenplum create user workflow works
Greenplum handles users and groups through one single role model in the database catalog. A user is just a role that has the right to log in. When an admin sets up a new role, the coordinator node records the entry. The coordinator then sends that role change to every segment host in the cluster. Users always log in through the coordinator node and never touch segment nodes directly.
After you make the role, you must update the host client access file. This file tells the coordinator which IP addresses and roles can log in. You also choose how the user proves who they are, like passwords or directory keys. Next, the admin grants schema and table rights to a group role. Individual login roles join that group role to inherit those table permissions. Admins also link the role to a resource group or queue. This step caps memory and CPU use so one user cannot slow the cluster.
What native roles solve and what they miss
Native database roles do a great job of blocking strangers at the front door. They check who logs in and control which schemas a role can open. Resource groups also stop heavy queries from taking all the cluster memory. For basic table boundaries, the built-in catalog rules work well.
Still, static database roles leave big security gaps during daily work. A role decides who logs in, not what a query does in flight. Once a user has read rights on a customer table, they see every column by default. Native table grants cannot rewrite emails, phone numbers, or card numbers in query results. If an engineer needs to fix one broken row, they get full write rights. That standing permission stays active long after the ticket closes. Shared role passwords also sit on laptops and inside app config files. When five people share one role, the database log cannot show who ran a drop command.
User Provisioning (SCIM) + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Why standing permissions create risk for data teams
Data warehouses hold huge volumes of records across hundreds of tables. Managing fine permissions for every single person takes hours of manual admin work. To save time, teams grant broad schema rights to general roles. Soon, dozens of people and scripts can read or change critical business tables. Auditing these nested role trees becomes a slow chore during security checks.
Revoking rights is also hard because admins fear breaking nightly data jobs. So old accounts keep their high permissions for months or years. A stolen password or a bad script can then wipe out key data fast. Teams need a way to check queries and hide private fields on the fly. They also need clear logs tied to real people instead of shared database roles.
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 Greenplum?
Greenplum treats users and roles as the exact same catalog object. The only difference is that a user role starts with login rights turned on.
Why can a new Greenplum user not log in after creation?
Making the role in the catalog is only the first step. An admin must also add the role and network address to the coordinator host access file.
How do teams limit CPU and memory for a new Greenplum user?
Admins assign the user role to a specific resource group or resource queue. This setting caps how many queries and how much memory that role can use at once.
Related guides
In this post