Select a documentation version: <button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">15.7.1</button>

- [Current (18.4.0)](https://docs.cloud.google.com/alloydb/omni/kubernetes/current/docs/database-users/overview.md.txt)
- [18.4.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.4.0/docs/database-users/overview.md.txt)
- [18.3.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.3.0/docs/database-users/overview.md.txt)
- [18.1.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.1.0/docs/database-users/overview.md.txt)
- [17.10.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.10.0/docs/database-users/overview.md.txt)
- [17.9.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.9.0/docs/database-users/overview.md.txt)
- [17.7.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.7.0/docs/database-users/overview.md.txt)
- [17.5.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.5.0/docs/database-users/overview.md.txt)
- [16.14.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.14.0/docs/database-users/overview.md.txt)
- [16.13.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.13.0/docs/database-users/overview.md.txt)
- [16.11.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.11.0/docs/database-users/overview.md.txt)
- [16.9.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.9.0/docs/database-users/overview.md.txt)
- [16.8.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.8.0/docs/database-users/overview.md.txt)
- [16.3.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.3.0/docs/database-users/overview.md.txt)
- [15.18.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.18.0/docs/database-users/overview.md.txt)
- [15.17.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.17.0/docs/database-users/overview.md.txt)
- [15.15.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.15.0/docs/database-users/overview.md.txt)
- [15.13.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.13.0/docs/database-users/overview.md.txt)
- [15.12.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.12.0/docs/database-users/overview.md.txt)
- [15.7.1](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.7.1/docs/database-users/overview.md.txt)
- [15.7.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.7.0/docs/database-users/overview.md.txt)

<br />

This page describes how AlloyDB Omni works with PostgreSQL roles. This page assumes that you are familiar with PostgreSQL.

<br />

An AlloyDB Omni database uses [the standard PostgreSQL concept of roles](https://www.postgresql.org/docs/current/database-roles.html). A role can act as a database user, a group of users, or both.

A *user role* has the `LOGIN` privilege that lets users sign in to the AlloyDB Omni system. A *group role* has member roles with various privileges, which you can grant to or revoke from all members at once.

## AlloyDB Omni predefined PostgreSQL roles

PostgreSQL has a set of [predefined roles](https://www.postgresql.org/docs/current/predefined-roles.html)
with various privileges. AlloyDB Omni adds several user and group
roles to this set of PostgreSQL's predefined roles.

The following table lists the PostgreSQL roles that AlloyDB Omni
predefines:

| Role name | Privileges |
|---|---|
| `alloydbadmin` | `SUPERUSER` (which includes `CREATEROLE`, `CREATEDB`, and `LOGIN`). |
| `alloydbmetadata` | By default, this role does not have any privileges. |
| `alloydbmonitor` | Provides the `pg_monitor` and `LOGIN` read-only monitoring privileges used by the AlloyDB Omni operator to collect database metrics. |

In addition, AlloyDB Omni reserves the following role names that are unused but may be used in the future.

| Role name | Privileges |
|---|---|
| `alloydbagent` | `NOLOGIN` |
| `alloydbexport` | `NOLOGIN` |
| `alloydbiamgroupuser` | `NOLOGIN` |
| `alloydbiamuser` | `NOLOGIN` |
| `alloydbimportexport` | `NOLOGIN` |
| `alloydbobservability` | `NOLOGIN` |
| `alloydbreplica` | `NOLOGIN` |
| `alloydbsqllogical` | `NOLOGIN` |
| `alloydbsuperuser` | `NOLOGIN` |

### The alloydbadmin user role

The `alloydbadmin` role is a predefined role that sets up
the database system and performs other superuser tasks. This role has the following privileges:

- Create extensions that require superuser privileges
- Create event triggers
- Create replication users
- Create replication publications and subscriptions

This role is only used by AlloyDB Omni internal tools and shouldn't be used by users.

### The alloydbmetadata role

The `alloydbmetadata` role is a predefined role with fewer privileges, also used by AlloyDB Omni internally. Similar to `alloydbadmin`, this role shouldn't be used by other users.

### The `alloydbmonitor` role

The `alloydbmonitor` role is a predefined read-only account used by the
AlloyDB Omni operator to gather database metrics. Similar to
`alloydbadmin`, this role is used internally by AlloyDB Omni.
Don't assign this role to other users.


## What's next

- [Manage AlloyDB Omni roles](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.7.1/docs/database-users/manage-users.md.txt)