The Role Editor window allows you to set role properties which are:
Role Name (User Name)
Set name of the new user.
Role ID (User ID)
Specify an ID for the user. This is normally not necessary, but
may be useful if you need to recreate the owner of an orphaned object. If
this is not specified, the highest assigned user ID plus one (with a minimum
of 100) will be used as default.
Note: In PostgreSQL versions 8.1 or above, the specified ID will be ignored, but is accepted for backwards compatibility.
Can login
Check this option to create a role that allow to login. A role having this option can be thought of as a user. Roles without this attribute are useful for managing database privileges, but are not users in the usual sense of the word.
Password
Set user's password.
Note: If you do not plan to use password authentication you can omit this option, but then the role will not be able to connect if you decide to switch to password authentication.
Confirm Password
Re-type the password here.
Password Encryption
This option control whether the password is stored ENCRYPTED or UNENCRYPTED in the system catalogs. (If neither is specified, the default behavior is determined by the configuration parameter password_encryption.)
Connection Limit
If role can log in, this specifies how many concurrent connections the role can make. -1 (the default) means no limit.
Expires Date
Set a date and time after which the user's password is no longer
valid. If this clause is omitted the password will be valid for all time.
Superuser
Check this option to determine the new role is a superuser, who can override all access restrictions within the database.
Can create database
Check this option to define a role's ability to create databases.
Can create role
Check this option to allow creating roles.
Inherit privileges
Check this option to determine whether a role inherits the privileges of roles it is a member of.
See also:
Setting Role Membership
Setting Role Member