User Fields

Tags control access. Fields carry information: a phone number, a start date, a badge level. Torii handles them with the same two-layer system as tags, and once you've seen one, the other follows.

Under Membership → Fields is the list of local fields and, next to each, the remote CRM field it's mapped to. Create a field with a name and a type. The supported types are text, date, and number.

A new field is local-only until you map it. Click the remote field column and your CRM's fields load in a picker; select one and the mapping is live. From then on, sync runs in both directions: a value updated on your site lands in the CRM, and a value the CRM changes shows up on your site.

An unmapped field still works locally. Nothing syncs, which is exactly what you want for internal bookkeeping that the CRM has no business knowing about.

Why the local field comes first

This is the part people skip and then wonder why nothing displays. The shortcodes that show or collect member data reference local fields, not CRM fields. If you want to display a value your CRM is storing, you create and map the local field first, then reference it. Same as tags: you always apply, remove, and display through the local layer, and the mapping handles the CRM behind the scenes.

The rule in one sentence: if a shortcode can't see it, map it.