PermissionId Enumeration

Details the PermissionId enumeration. Permission IDs can be used with the permission validation URLs:

• GET (/users/{requestorId}/permission/validate)
• POST (/users/{requestorId}/permission/validate)

These IDs include direct checks against a particular setting for a user, such as checking a single privacy setting of a target, or a single privilege actor. In addition, there are permission IDs that can be used with the permission API and incorporate checks against multiple settings for specific user actions.

Permissions

These are values that a caller can use to check whether a specific action can be performed. Unlike the settings above, these encapsulate policies defined by the service and cannot be directly changed by users, though in most cases, the policies build on top of one or more settings whose values are defined by users. These are usually composite checks against more than one setting defined above. Example: The ViewProfile permission does a check of the target's ShareProfile privacy setting and the requestor's AllowProfileViewing privilege.

In general, it's recommended that callers request a permission ID for actions that need to be checked, rather than directly checking privacy settings and privileges. This allows privacy policies to be changed consistently across the service as new checks are incorporated.