Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Power Platform Functional Consultant: PL-200 Exam Guide

You're reading from   Microsoft Power Platform Functional Consultant: PL-200 Exam Guide Learn how to customize and configure Microsoft Power Platform and prepare for the PL-200 exam

Arrow left icon
Product type Paperback
Published in Dec 2020
Publisher Packt
ISBN-13 9781838985684
Length 648 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Julian Sharp Julian Sharp
Author Profile Icon Julian Sharp
Julian Sharp
Arrow right icon
View More author details
Toc

Table of Contents (34) Chapters Close

Preface 1. Section 1: Introduction
2. PL-200 Exam FREE CHAPTER 3. Section 2: Microsoft Dataverse
4. Power Platform 5. Data Modeling 6. Business Rules 7. Classic Workflows 8. Managing Data 9. Dataverse Settings 10. Security 11. Section 3: Power Apps
12. Model-Driven Apps 13. Canvas Apps 14. Portal Apps 15. Section 4: Automation
16. Power Automate Flows 17. Business Process Flows 18. UI Flows 19. Section 5: Power Virtual Agents
20. Creating Chatbots 21. Configuring Chatbots 22. Section 6: Integrations
23. Power BI 24. AI Builder 25. Microsoft 365 Integration 26. Application Life Cycle Management 27. Tips and Tricks 28. Practice Test 1 29. Answers to Practice Test 1 30. Practice Test 2 31. Answers to Practice Test 2 32. Assessments 33. Other Books You May Enjoy

Owner teams

Owner teams can have security roles applied and can therefore own records and have records shared with the team. You create owner teams manually and add users as members of the team.

Every business unit has a team. This is known as the default team, and all users who belong to the business unit are automatically added as members of the default team. You cannot edit the default team or change its membership.

Teams must belong to a business unit but can have members from other business units. This is the method by which we can breach the strict hierarchy of the business unit/security role model. For instance, an owner team can be created for the Central business unit, but it might contain members from the Operations business unit. A record owned by this team will be accessible by members of the Operations business unit even if their security role provided only the business unit access level to the entity.

Sharing a record requires the user to access a non-intuitive...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image