# Embedding Discourse Profile via Javascript **URL:** \ **Category:** Feature\ **Created:** [November 26, 2015, 12:35am UTC](https://meta.discourse.org/t/embedding-discourse-profile-via-javascript/36030 "2015-11-26T00:35:12Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\ **Post date:** [November 26, 2015, 2:36pm UTC](https://meta.discourse.org/t/embedding-discourse-profile-via-javascript/36030/3 "2015-11-26T14:36:05Z")
What you’re talking about is a super tight SSO integration. I don’t know if we have any examples of anyone going to quite this length, but it should be doable just using the Discourse API. You most likely don’t wanna be embedding user preferences in other pages. I think the idea of a 100% centralised profile is a pipe dream though. Literally _no one_ does this, because **centralisation** eventually needs to make way for **context**. There’s some overlap between your Google Plus profile and your YouTube account for instance, but managing your YouTube notification preferences, followed channels etc. makes a whole lot more sense in the _context of YouTube_ as opposed to inside Google Plus. I wouldn’t want things like my Discourse e-mail notifications or “Consider new when” preferences in a non-Discourse page. That easily gets super confusing. I can get behind a hybrid system though, which some Discourse sites are already doing to varying degrees. Like: Lock up the following options in preferences: - Username - Name - Email - Password - Profile picture - Profile background - User card background - Interface language - About me - Location - Website And only make them editable through a parent profile which is set up as the SSO provider. --- _[View the full topic](https://meta.discourse.org/t/embedding-discourse-profile-via-javascript/36030)._