{"id":39780,"date":"2024-11-27T15:03:05","date_gmt":"2024-11-27T09:33:05","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=39780"},"modified":"2024-11-29T11:42:29","modified_gmt":"2024-11-29T06:12:29","slug":"simplifying-site-security-how-the-new-power-pages-security-workspace-enhances-site-protection","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2024\/11\/simplifying-site-security-how-the-new-power-pages-security-workspace-enhances-site-protection\/","title":{"rendered":"Simplifying Site Security: How the New Power Pages Security Workspace Enhances Site Protection"},"content":{"rendered":"

\"Power<\/p>\n

As an administrator at a technology company, one of my main responsibilities is ensuring that sensitive customer data is protected and that only the right people have access to selected areas of the system. However, with multiple users, roles, and sites in Dynamics 365, keeping track of who can access what and making sure everything stays secure can be too challenge.<\/p>\n

A few months ago, we had a situation where an employee accidentally gained access to sensitive data they should not have due to poorly managed site security settings. This created a security risk and required a lot of time to fix it.<\/p>\n

How the Feature Helps: <\/strong><\/p>\n

This is where the new “Security Workspace” feature in Design Studio really came in handy. With the Security Workspace, I was able to easily manage and control access rights across different page sites in our system. The workspace provides a visual and streamlined interface to review and adjust security settings for users, roles, and permissions for sites, pages, and websites without needing to deep dive into the complex configurations and settings.<\/p>\n

We have several teams within our sales department that need access to different sets of customer data. Some need access to all customer details, while others only need limited information. Before the Security Workspace, managing these varying levels of access was time-consuming and led to human errors. With this new workspace, I was able to quickly create specific security roles for each team and securely assign the right permissions to the right people.<\/p>\n

One day, when a new member of our sales team joined, I was able to set up their permissions in just a few clicks using the Security Workspace. Instead of manually checking and updating access rights across multiple areas, the Security Workspace helped me visualize the access layers in a centralized view, reducing the chance of errors. This saved a lot of time, and it ensured that only the right people had access to sensitive information.<\/p>\n

Here\u2019s a step by step guide:<\/p>\n

Web Roles<\/strong><\/p>\n

A web role is basically a collection of permissions to the access content of a site. Web role is an important factor for managing user access and ensuring that each user can only see and interact with the specific page of the site relevant to them. This helps in maintaining the security and organization within the site.<\/p>\n

Here are the steps on how to create Web roles.<\/p>\n

    \n
  1. Navigate to Power Pages Site.<\/li>\n
  2. In the Left navigation Pane, click on Security –> Web roles –> Add new role <\/strong>as shown in screenshot.<\/li>\n<\/ol>\n

    \"Power<\/p>\n

      \n
    1. After Clicking on New role,<\/strong> it will be redirected to the Power Pages Management<\/strong> App. Complete the necessary information and select the Save<\/strong> button.<\/li>\n<\/ol>\n

      \"Power<\/p>\n

      Now, Admin<\/strong> Web role has been created and can be seen in the Power Pages Web role<\/strong> section.<\/p>\n

      \"Power<\/p>\n

      To manage access to these webpages effectively, specific web roles have been created, like Admin, Anonymous users, Authenticated users, System users, etc.<\/strong><\/p>\n

      Page Permissions<\/strong><\/p>\n

      Set page permissions to either make content accessible to all visitors on your site or limit access to users with designated roles.<\/p>\n

      Select the page that you want to give the permissions->>Edit permissions.<\/p>\n

      \"Power<\/p>\n

      Select the role that can view the page->>Save.<\/p>\n

      \"Power<\/p>\n

      \u00a0<\/strong>Now the page permissions have been set.<\/p>\n

      \"Power<\/p>\n

      Table permissions<\/strong><\/p>\n

      To allow access to Microsoft Dataverse records configure\u00a0and\u00a0assign\u00a0table permissions.<\/p>\n

      Click on Table permissions->>New permission.<\/p>\n

      \"Power<\/p>\n

      Now you can choose the table from Dataverse, then give permissions and roles that you want. Click on save.<\/p>\n

      \"Power<\/p>\n

      In the below screenshot, you can see the overview of table permissions.<\/p>\n

      \"Power<\/strong><\/p>\n

      Site Visibility<\/strong><\/p>\n

      Control access to your site with\u00a0site visibility. Power Pages sites can be configured as either private or public, depending on your access requirements. As well, you can add or remove specific people for site access.<\/p>\n

      \"Power<\/strong><\/p>\n

      Conclusion<\/strong><\/h2>\n

      In conclusion, adding role-based access control (RBAC) in Power Pages has made a big difference for our organization. By setting clear user permissions, we\u2019ve boosted security and minimized the risk of data breaches. This change not only safeguards sensitive client information but also makes the application process smoother and more user-friendly for both clients and our team.<\/p>\n

      \"Microsoft<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

      As an administrator at a technology company, one of my main responsibilities is ensuring that sensitive customer data is protected and that only the right people have access to selected areas of the system. However, with multiple users, roles, and sites in Dynamics 365, keeping track of who can access what and making sure everything\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1913,2763],"tags":[2743,2969],"class_list":["post-39780","post","type-post","status-publish","format-standard","hentry","category-microsoft-power-platform-services","category-power-pages","tag-power-pages","tag-power-pages-security-workspace-enhances-site-protection"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/39780","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=39780"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/39780\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=39780"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=39780"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=39780"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}