> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fly.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Users & Roles

<Warning>
  **This page is archived.** Fly Postgres (unmanaged) is no longer maintained, and Fly.io Support is not able to provide support or guidance for it. We now offer [Fly.io Managed Postgres](/postgres), our fully-managed database service that handles all aspects of running production PostgreSQL databases.

  These pages are kept for reference and are not listed in the navigation. The full set is indexed on the [Fly Postgres (Unmanaged)](/unmanaged-postgres) page.
</Warning>

A Postgres cluster is configured with three users when created:

* `postgres` - a role with superuser and login privileges that was created for you along with the cluster. Since the `postgres` role has superuser rights, it's recommended that you only use it for admin tasks and create new users with access restricted to the minimum necessary for applications
* `flypgadmin` - a role used internally by Fly.io to configure and query the Postgres cluster
* `repmgr` - a role used by repmgr to manage replication for the Postgres cluster

If you [attached a Fly App](/unmanaged-postgres/managing/attach-detach) to your Postgres cluster app with `fly postgres attach`, then you'll have a an additional database and user with the same name as the consuming app.

You can list users with flyctl. For example, for a Postgres cluster app named `pg-test`:

<CodeGroup>
  ```bash cmd theme={null}
  fly postgres users list --app pg-test
  ```

  ```output output theme={null}
  NAME          	SUPERUSER	DATABASES
  my_app_name	    yes      	my_app_name, postgres, repmgr
  flypgadmin    	yes      	my_app_name, postgres, repmgr
  postgres      	yes      	my_app_name, postgres, repmgr
  repmgr        	yes      	my_app_name, postgres, repmgr
  ```
</CodeGroup>

In this example, there's an attached Fly App in the list of users.