Power Platform Community Forum Thread Details

I aim to simplify the example for clarity. Imagine we have 10 agents, each with their own set of cases. Additionally, there are two managers who must have the capability to handle any case from the pool of agents, should an agent be unavailable. Is this a scenario you’ve encountered before? If so, how was it addressed? My research, including AI recommendations, suggests a particular solution. However, I would prefer to reference a practical demonstration, such as a blog post or a video, that showcases this solution in action.

BING AI Result:
1 Understanding Portal Security:
◦ In Power Pages, security is based on table permissions and web roles.
◦ Each table permissionacts like a key, allowing access to specific records.
◦ A web role is a set of keys (table permissions) assigned to portal users (Contacts).
2 Contacts and Relationships:
◦ Portal users are actually Contacts.
◦ Row-based security is determined by the relationship between the logged-in Contact (or their Account) and the record.
◦ Unlike Dynamics 365, ownership doesn’t play a role in portal security.
3 Scenario: Person A (On Vacation) and Person B (Designated Access):
◦ You want Person B to access Person A’s records during vacation.
◦ Here’s how you can set it up:
4 Table Permissions:
◦ Ensure that the relevant tables (e.g., cases) have a direct relationship to the Contact or the Contact’s Account.
◦ For example:
▪ If Person A is the customer (Contact), the case table should have a relationship to the Contact.
▪ If Person A’s Account is the customer, the case table should have a relationship to the Account.
5 Web Roles:
◦ Create a custom web role (e.g., “Case Worker”) for Person B.
◦ Associate the necessary table permissions (keys) with this web role.
◦ These permissions should allow Person B to read and update cases related to Person A.
6 Assign Web Role to Person B:
◦ Assign the “Case Worker” web role to Person B.
◦ Now Person B has the keys (table permissions) to access Person A’s cases.
7 Testing and Monitoring:
◦ Test the setup thoroughly.
◦ Ensure that Person B can view and work on Person A’s cases.
◦ Monitor any changes or adjustments needed.
Remember that this approach allows secure access to specific records based on relationships. Person B will be able to open Person A’s requests while maintaining security.