Weekly Patch - November 22, 2026
Notifications
Resize the formatting editor in Standard emails and custom messages
What's new: Last week the custom message on notifications picked up formatting. This week it gets some room to breathe. The formatting editor for Standard emails and for custom notification messages (activity announcements and reminders, and phase date changes) used to be stuck at about six lines, so a longer note meant scrolling around inside a tiny box. Now you can resize it vertically, just like the editor for Custom emails.
See it in action:
- From your Surveys, Tasks, Content, or Releases list, use the Notify users action on an item and choose Use custom message.
- Grab the handle at the bottom edge of the editor and drag it down to make the editor taller, or back up to make it shorter.
- Write your note with the whole thing in view. The email your recipients get looks exactly the same either way. 🎉
Good to know:
- The editor resizes up and down only, and it won't go shorter than its starting height.
- Your chosen height isn't saved. The editor returns to its starting size the next time the page loads.
- The resize handle is built for a mouse, so it may not respond to touch.
Content
Every tester gets their own distributed value
What we fixed: Distributed values (the keys or codes you hand out to testers through content) could occasionally go to two testers at once. It happened when lots of testers opened the same content at the same moment, like right after a big invite lands and everyone hits a click-through notice, or when an admin saved the value list while values were being handed out. Not anymore: each value now goes to exactly one tester, or to no more testers than you've allowed with a self-select group's Users per value setting.
See it in action:
- As an admin, add an auto-assign distributed value group to a content item (or notice), paste in your list of keys, and publish it to your testers.
- Have your testers open the content. Each one gets a different key, and it stays the same every time they come back.
- Need to add more keys while testers are already getting theirs? Go for it. Open the group, add to the list, and save. Keys already handed out stay with their testers and never go back into the pool. No more awkward "we both got the same code" emails. 🎉
Good to know:
- If you paste the same key twice in one save, it's only added once. A key that's already in the group isn't added again either.
- Keys that differ only in upper or lower case (like
ABC-1andabc-1) still count as different keys. - Want one key shared by several testers? Use the group's Users per value setting rather than pasting the key multiple times.
- Keys that were already given to two testers before this fix stay where they are. Nobody loses a key they already have.
User Accounts
Alternate names from single sign-on now behave like the rest of your SSO fields
What we fixed: If your site uses alternate first and last names, your sign-in provider can now fill them in for members, the same way it fills email and name. OAuth SSO setups couldn't map those fields at all, and a value set behind the scenes got wiped the next time anyone saved the configuration. On SAML setups, members could edit the alternate names your provider sent, and marking them as required didn't actually do anything. All fixed! 🔒
See it in action:
- Make sure alternate names are on: in your community's User account settings, check Include alternate first & last names.
- Open Single sign-on management and edit your OAuth configuration. You'll now see Alternate first name parameter and Alternate last name parameter, each with its own Identity Provider (IdP) must supply this value checkbox. Fill them in, save, and they stay put, even through later saves.
- Have a member sign in through SSO and open My account settings. Any alternate name your provider sent is locked in place, just like their email and name. Alternate names your provider didn't send stay editable. No more "creative" self-edits to values you rely on. 😉
Good to know:
- If a configuration marks an alternate name as required and your provider doesn't send it, the sign-in stops with a "missing information" message. That's the same thing that happens with a missing first or last name. Heads up for SAML sites: a new SAML configuration has these boxes checked by default, so if your provider doesn't send alternate names, uncheck them or those sign-ins will stop.
- New OAuth configurations also start with both alternate name boxes checked. Uncheck them if your provider won't send these values.
- Alternate name fields only show up in your SSO settings while Include alternate first & last names is on. If you turn it off and then save an OAuth configuration, its alternate name parameters are cleared, so re-enter them after turning the option back on.