<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permission Conflicts on</title><link>https://docs.protegrity.com/10.0/docs/pmg/pmg_creating_deploying_policies/policy_permissions/permission_conflicts/</link><description>Recent content in Permission Conflicts on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/10.0/docs/pmg/pmg_creating_deploying_policies/policy_permissions/permission_conflicts/index.xml" rel="self" type="application/rss+xml"/><item><title>Inheriting Permissions</title><link>https://docs.protegrity.com/10.0/docs/pmg/pmg_creating_deploying_policies/policy_permissions/permission_conflicts/pmg_inheriting_permissions_for_users_in_multiple_roles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.0/docs/pmg/pmg_creating_deploying_policies/policy_permissions/permission_conflicts/pmg_inheriting_permissions_for_users_in_multiple_roles/</guid><description>&lt;p>A special case exists when a user is present in multiple roles, this creates a conflict. This section provides information about how the software resolves this conflict. As a general rule, the software applies the most restrictive permissions.&lt;/p>
&lt;p>Typically, when a policy user is assigned a role that does not have a specific data element associated with the role, then the user cannot use the data element for performing security operations. If the user tries to use the data element, then an error is generated.&lt;/p></description></item></channel></rss>