Hello!
I am creating a database and I am not sure how I should design the data to manage security. I don't know much about the details of Dataverse so I am going to explain it on a high level. I would also prefer if the solution could be done using just Dataverse/Power Apps to reduce complexity but if there is a much easier way with a plugin I would be happy to hear, thanks.
Here is the challenge:
I want a Project table that will have projects that are in the stages {opportunity, proposal, in-design, completed}.
I want to create security groups such as "Owner", "Manager", "Worker" , etc.
The Project table will have column names such as projectID, deadline date, client phone number, etc.
The database admin should be able to assign permissions based on the columns and the project stage.
An example would be:
Owner can see all stages and column names.
Worker can see only some of the project stages and only some of the column names.
So far I have 2 options to take:
Option 1: I thought maybe I could create views for each table and then assign groups to the views but it doesn't seem like that is a possibility without 3rd party plugins.
Option 2: My other thought was to create different tables based on the project stage and reference the projectID. Then just assign groups to to the project stages they need, and the columns within the table they need. This second option sounds like more work to maintain but maybe it is better practice, I am not entirely sure.
It would be great hear some advice,
Thanks in advance, all the best!
Jason
Solved! Go to Solution.
you got a requirement that is not complex but the options you have inside Dataverse are limited for your scenario.
I know Dataverse is not perfect and probably you got assigned to this task with "you need to use Dataverse", so I tell you some key points about security and after you can try to find out a solution to your scenario.
First thing is that you can assign security roles to a user or a team, this security role block or allow the entire record access. I do an example: You have two accounts, one owned by Bob one by Charlie. Let's imagine you are Bob, if your security role says: you can access all the accounts, you can see both accounts, if your security role says: you can access only your own accounts, you can see the account owned by you (Bob) but not the one owned by Charlie.
The second thing is Field Level Security. You can decide for each column if there is a permission on who can see the value of that record or not.
Let's say inside the account there is a phone number field. With Field Level Security you can say: only Administrator team can see the value, if you (Bob) you are not inside this team, you can still open the record but the phone number field will appear as ***.
Keep in mind that assign security roles is something done at administration level, it is possible to create some logic to dynamically assign security roles but is a path I don't recommend to do, especially if you are starting with Dataverse.
I hope what I wrote can help you to think about the scenario you have.
you got a requirement that is not complex but the options you have inside Dataverse are limited for your scenario.
I know Dataverse is not perfect and probably you got assigned to this task with "you need to use Dataverse", so I tell you some key points about security and after you can try to find out a solution to your scenario.
First thing is that you can assign security roles to a user or a team, this security role block or allow the entire record access. I do an example: You have two accounts, one owned by Bob one by Charlie. Let's imagine you are Bob, if your security role says: you can access all the accounts, you can see both accounts, if your security role says: you can access only your own accounts, you can see the account owned by you (Bob) but not the one owned by Charlie.
The second thing is Field Level Security. You can decide for each column if there is a permission on who can see the value of that record or not.
Let's say inside the account there is a phone number field. With Field Level Security you can say: only Administrator team can see the value, if you (Bob) you are not inside this team, you can still open the record but the phone number field will appear as ***.
Keep in mind that assign security roles is something done at administration level, it is possible to create some logic to dynamically assign security roles but is a path I don't recommend to do, especially if you are starting with Dataverse.
I hope what I wrote can help you to think about the scenario you have.
Thank you, I think I will try to have team security roles and then have column level security based on the team security roles. Thanks again!
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages