Connect several social accounts to one community, and gate their quests by role
Connect more than one account per social network to a community, set each one's quests and XP on its own, and limit which traders see them by role.
01 ·Connect several social accounts and gate each one's quests by role
A community can now hold more than one account per social network. After a broker connects the first account, a panel appears to add or select another, drawing on the broker's already-connected accounts or opening a fresh connection. Each connected account gets its own quest page, where a broker picks the posts it draws from and sets the XP for each. The same page carries a permission setting, so a broker limits an account's quests to traders holding chosen roles.
A broker who runs separate accounts for separate markets wants each one's quests in front of the right traders, not all of them in front of everyone. Holding several accounts and gating each one's quests by role lets a broker point a country's audience at the account that speaks to them while the rest stays out of view.
02 ·Send a badge request out over a webhook
A new outgoing webhook fires when a trader submits a badge request. It carries the badge requested and its description, the text and any attachment the trader sent, the trader's username and display name, and the time of the request, so a broker's own systems pick up the request as it comes in.
A broker who reviews badge requests outside the community wants each one to reach the tool they work in without watching the queue themselves. Sending the request out over a webhook lets a broker route it into a review or support system the moment a trader files it.
Store management was carried over to the rebuilt community settings, with set voucher and category image sizes.
7 Apr