{"_id":"555cb6ad7e271d0d00f3c9c1","initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"project":"545137a814af501a00b50cf9","user":{"_id":"5433099f9a2b451a00ad4531","username":"","name":"Ryan Braastad"},"tags":[],"__v":0,"createdAt":"2015-05-20T16:30:37.336Z","changelog":[],"body":"We’ve made a couple of changes to improve the privacy control permissions for [Open Graph Objects](https://developer.yammer.com/v1.0/docs/open-graph) (OGO) metadata. Previously, if you wanted a private Open Graph Object (OGO) you were required to specify the users who were able to see that object through OGO configuration. We wanted to allow for simplified privacy control when using OGOs.  \n \nNow, you are able to specify the OGOs to private and public groups. This means that OGO and metadata related to the OGO, respects the privacy of the group in which they are posted.  For instance, a new OGO posted to a private group from [Yammer Embed](https://developer.yammer.com/v1.0/docs/embed), will only be visible to members of that private group, and will only show up for those users within search. If a user is removed from the private group they will no longer be able to see the OGO and conversations related to that OGO. The general case is if you have access to Yammer comments on an OGO, you have access to the OGO metadata. \n  \n\nWe think this is a more intuitive way to use and control Open Graph Objects.  Additional information can be found in our documentation:  \n\nhttps://developer.yammer.com/v1.0/docs/commenting \nhttps://developer.yammer.com/v1.0/docs/messages-json-post\n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\nBy The Yammer Platform Team. Posted on May 20, 2015","slug":"enhanced-permissions-for-open-graph-objects","title":"Enhanced Permissions for Open Graph Objects"}

Enhanced Permissions for Open Graph Objects


We’ve made a couple of changes to improve the privacy control permissions for [Open Graph Objects](https://developer.yammer.com/v1.0/docs/open-graph) (OGO) metadata. Previously, if you wanted a private Open Graph Object (OGO) you were required to specify the users who were able to see that object through OGO configuration. We wanted to allow for simplified privacy control when using OGOs. Now, you are able to specify the OGOs to private and public groups. This means that OGO and metadata related to the OGO, respects the privacy of the group in which they are posted. For instance, a new OGO posted to a private group from [Yammer Embed](https://developer.yammer.com/v1.0/docs/embed), will only be visible to members of that private group, and will only show up for those users within search. If a user is removed from the private group they will no longer be able to see the OGO and conversations related to that OGO. The general case is if you have access to Yammer comments on an OGO, you have access to the OGO metadata. We think this is a more intuitive way to use and control Open Graph Objects. Additional information can be found in our documentation: https://developer.yammer.com/v1.0/docs/commenting https://developer.yammer.com/v1.0/docs/messages-json-post [block:api-header] { "type": "basic" } [/block] By The Yammer Platform Team. Posted on May 20, 2015