Is it possible to restrict permission of user at table level? Here is the scenario:
1. User needs access to create tables and columns in dataverse
2. User should not be able to customize other custom table (add/edit columns, read access is fine)
Hope you are doing good.
We can customize this type of behavior using Security Roles in Dataverse Environment.
Please follow below steps to proceed further.
1. Navigate to https://make.powerapps.com
2. Click Gear Icon at the Top --> Select Advance Settings
3. Once Advance settings Page Loaded --> Select Settings --> Select Security
4. Click Security Role
5. Open any Existing or Click New to Create a new Security Role
6. If it is a Custom Entity Navigate to Custom Entity Tab else you can find the Table Name in Core Records
These are the below Key Behavior Available in Dataverse
If We Provide Create/Read/Write/Delete as User Level then Logged in User Can Create Record and he can Only Read his Record/ Delete and Write the Record
Business Unit --> Users in his respective BU can perform the same operation who ever creates
Same way for Parent Child
Organization --> Any One can Create/Read/Write/Delete record because he is having Global Level Access
For More Information : https://docs.microsoft.com/en-us/power-platform/admin/wp-security-cds
Please mark as Answer if it is helpful and provide Kudos
Hello @rampprakash ,
Thank you for your update. Above solution will only hide data inside a table to user based on the permission we granted.
We have to provide access to user to create columns at particular table level. What we did was granted access to "Field" at customization tab which will in turn grant access to all tables. But we are looking for this permission at a single table
Hi @PRAVEENZNMD ,
You will need to do this through solutions and managed properties. Please review the following: https://docs.microsoft.com/en-us/power-platform/alm/managed-properties-alm
Hi @PRAVEENZNMD ,
Be conscience that the solution with these tables / resources that you want to make read-only in the environment would need to be managed solutions so they would need to be developed in a different environment and promoted to the environment you are discussing above with the appropriate managed property configuration. If you were all developing in only one environment then you would not be able to restrict that I know of... Please review the solution concepts here: https://docs.microsoft.com/en-us/powerapps/maker/data-platform/solutions-overview
Hope this works well for your needs.
Keep up to date with current events and community announcements in the Power Apps community.
Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.
Check out the latest Community Blog from the community!