PL-400 Exam Prep: Understanding Security in Microsoft Dataverse

Поділитися
Вставка

КОМЕНТАРІ • 16

  • @nathan5657
    @nathan5657 10 місяців тому

    Slight changes have occured for the copy role action, these are the steps to follow at the time of writing:
    Select the (basic user) role from the "Security Roles" screen and then select More Actions -> Copy Role

  • @sgeorge1642
    @sgeorge1642 3 роки тому +1

    Great video. Thanks very much.

  • @nice2skate
    @nice2skate 3 роки тому +1

    Well done

  • @netsena1775
    @netsena1775 Рік тому

    thanks Joe!

  • @johnbrennan8442
    @johnbrennan8442 2 роки тому

    Great video can I ask how to prevent other members of an environment from seeing your solution / tables please

    • @CRMChap
      @CRMChap  2 роки тому

      It's not possible to selectively control which user(s) can see and work with specific solutions, it's an "all or nothing" approach. The only way to implement something like this would be by using separate environments.

    • @johnbrennan8442
      @johnbrennan8442 2 роки тому

      @@CRMChap Thank you for the reply it’s not good that every developer can see each other’s solutions within our specified Dev env and not practical to have every developer have their own dev env

    • @CRMChap
      @CRMChap  2 роки тому

      This is actually better this way IMHO, because otherwise, how will developers know whether someone else has modified or altered the same component? 😉 Developers can setup their own personal environment free of charge via the developer plan, and this is the recommended approach to follow:
      docs.microsoft.com/en-us/powerapps/maker/developer-plan

    • @johnbrennan8442
      @johnbrennan8442 2 роки тому

      @@CRMChap We don’t want our developers having their own Dev Envs as they could bypass our governance easily

    • @CRMChap
      @CRMChap  2 роки тому

      Well, regardless, your developers can (if they want to) set up a Developer Plan environment at any time. And you have, as far as I know, no control or visibility over this. So my question would be, why is this such a huge governance concern for you?

  • @belkaaloulwahiba4770
    @belkaaloulwahiba4770 2 роки тому

    excellent very useful

  • @MrCybergoku
    @MrCybergoku 3 роки тому

    Thanks !

  • @side54723
    @side54723 3 роки тому

    Great video.
    Assuming ive set my entity permission. Where my record are shared with my team.
    Is it possible, lets say for a record, where a type is "for everyone" (a field created called type), would be shared to everyone.
    Or same question to share this record to a business unit instead.
    Thank you

    • @CRMChap
      @CRMChap  3 роки тому +1

      Hi Jeff, as far as I know, this would only be possible to do via code - on change of this field, you can then execute a request to share the record with all users in a business unit. Alternatively, you would have to create the table as Organization owned, but this would mean that no owner could ever be assigned to it and you would have to grant full or no access. Here are some articles on these topics:
      docs.microsoft.com/en-us/powerapps/developer/data-platform/security-sharing-assigning?WT.mc_id=BA-MVP-5003861
      docs.microsoft.com/en-us/powerapps/developer/data-platform/webapi/use-web-api-actions?WT.mc_id=BA-MVP-5003861
      docs.microsoft.com/en-us/powerapps/maker/data-platform/types-of-entities#standard-tables?WT.mc_id=BA-MVP-5003861
      Hope this helps 😀

    • @side54723
      @side54723 3 роки тому

      @@CRMChap thank you ill explore that !