# Provide select access to future objects

**URL:** <https://forum.ansible.com/t/provide-select-access-to-future-objects/32991>\
**Category:** Ansible Project\
**Created:** [May 20, 2020, 8:51pm UTC](https://forum.ansible.com/t/provide-select-access-to-future-objects/32991 "2020-05-20T20:51:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Banti\_Kr](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@Banti\_Kr](https://forum.ansible.com/u/Banti_Kr)\
**Post date:** [May 20, 2020, 8:51pm UTC](https://forum.ansible.com/t/provide-select-access-to-future-objects/32991/1 "2020-05-20T20:51:11Z")

</div>

Hi,  
I am using ansible-playbook to create a dev user which should have only read access in PostgreSQL but after creating dev user, the user is able to perform DML commands within his user scope and also not able to read to future objects or tables means the dev user can't access the tables created from root user. How I can restrict dev user to create/insert/update/delete and other DML commands and allow to access future objects. This is what I am using:

- database: testDB  
&nbsp;&nbsp;&nbsp;grant\_option: no  
&nbsp;&nbsp;&nbsp;objs: ALL\_IN\_SCHEMA  
&nbsp;&nbsp;&nbsp;state: present  
&nbsp;&nbsp;&nbsp;privs: select  
&nbsp;&nbsp;&nbsp;type: table  
&nbsp;&nbsp;&nbsp;role: read\_only\_role

---

<div class="post-metadata">

**Author:** ![Dick\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@Dick\_Visser](https://forum.ansible.com/u/Dick_Visser)\
**Post date:** [May 20, 2020, 10:12pm UTC](https://forum.ansible.com/t/provide-select-access-to-future-objects/32991/2 "2020-05-20T22:12:07Z")

</div>

> Hi,  
> I am using ansible-playbook to create a dev user which should have only read access in PostgreSQL but after creating dev user, the user is able to perform DML commands within his user scope and also not able to read to future objects or tables means the dev user can’t access the tables created from root user. How I can restrict dev user to create/insert/update/delete and other DML commands and allow to access future objects. This is what I am using:
> 
> - database: testDB  
> grant\_option: no  
> objs: ALL\_IN\_SCHEMA  
> state: present  
> privs: select  
> type: table  
> role: read\_only\_role

What is this? A snippet from a playbook?  
Because there is no task called ‘database’.  
Post your entire playbook.