# Create a read-only user in PostgreSQL

To create a read-only user in PostgreSQL, you can follow these steps:

1. Connect to your PostgreSQL database as a user with sufficient privileges, such as the superuser or a user with the `CREATEROLE` privilege.
2. Open a SQL client or a terminal and execute the following SQL statement to create a new user.&#x20;

   Replace `'password'` with the desired password for the read-only user:

<pre class="language-sql"><code class="lang-sql"><strong>CREATE USER readonly_user WITH PASSWORD 'password';
</strong></code></pre>

3. Grant the necessary privileges to the read-only user. In this case, we want the user to have only read access to specific tables. Execute the following SQL statement to grant `SELECT` privileges on the desired tables, Replace `table_name` with the name of the table you want to grant read access to. Repeat this step for each table you want to include:

```sql
GRANT SELECT ON table_name TO readonly_user;
```

4. Finally, you can create credentials with the new read-only user to test the access. The read-only user should be able to connect to the database and perform `SELECT` queries on the granted tables but will not have permission to modify the data.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bipeye.com/product-docs/overview/credentials/databases/postgressql/create-a-read-only-user-in-postgresql.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
