# Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso)

**URL:** https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045
**Category:** Integrations
**Tags:** sso, discourseconnect, configuring, how-to
**Created:** [February 25, 2014, 8:30am UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045 "2014-02-25T08:30:34Z")
**Posts on this page:** 1
**Showing post:** 623

<div class="post-metadata">

### Author: ![adopilot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adopilot/32/105040_2.png) [@adopilot](https://meta.discourse.org/u/adopilot)
#### Post date: [November 13, 2025, 12:50pm UTC](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/623 "2025-11-13T12:50:43Z")

</div>

> [@Discourse](#):
>
> ### Advanced Features
> 
> - You can pass through custom user fields by prefixing the field name with `custom`. For example `custom.user_field_1` can be used to set the value of the `UserCustomField` that has the name `user_field_1`.

Is there any convention or rules how to encode user field names.

If my custom user fields are named as eg:

- Šifra za kasu
- Vaše radno mjesto

How I should format my payload Do i need to urlencode name or is enough to use snake case only

---

_[View the full topic](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045)._
