getPermissionPolicy

Permission being defined

More complex policies can be defined with a set of assertions

Must the user authenticated?

Is this permission gated to a specific availability? This is used to limit access to features that are not yet available in production

Parent permissions this permission is dependent on

Can an entity provide additional conditions to further limit access?

Can the user delete the entity being accessed?

Is the user an owner of the entity being accessed?

Must the user be the owner of the entity being accessed?

Is this permission gated to a specific environment? (e.g. devext, qaext) This is used to limit access to features that are not yet available in production

Value set by the feature flagging system to override the default permission behavior. This can be used to demo features to specific users or groups, during a specific user session. If true, the permission will be granted as long as the license and privilege requirements are met. If false, the permission will be denied for all users - typically as a means to check for graceful degradation if a system is offline.

What licenses are required for this permission to be granted. This is checking the licese of the current user's org. It is not transitive to the entity being accessed. e.g. If a user is in a Partner "hub-basic" org, they can not create "premium" entities (e.g. Projects)

Any platform level privileges required for this permission to be granted e.g. "portal:user:createItem"

What services are required to be online for this permission to be granted