With member campaigns you can now also give the option (or make it required) to your members to add a link to their campaign. In this example, we show you how it works.

As a member I would like to receive more comments on my post on LinkedIn. So I can create a campaign in Ambassify to ask my fellow ambassadors to leave a comment on my post.

We've separated the authentication providers for login and registration. This makes it easier to phase out authentication providers you don't want to use in a community anymore.

By disabling the provider for registration but leaving it on for login, new members won't be able to register with it anymore while existing members will still be able to log in.

Activity from members using Microsoft Teams is now tracked separately from other channels. You can now see Teams usage when you split a report by "Channel" or filter on Teams usage using the "Channel" filter.

We moved the Microsoft Teams integration out of beta and it is now available to all Premium and Enterprise customers. You can enable and install it through the "Integrations" settings in manage.

We added the option to upload multiple images or videos when creating a campaign that includes sharing on Google Business.

Note that Google Business does not support these types of media, so the resulting share will instead be a link to an Ambassify page where visitors can see the album or watch the video. This is identical to how it works when users share this kind of media on their personal Facebook profile, for example.

We've extended the lifetime of our 3rd party account connections, meaning users will have to reconnect their accounts less often.
​

A recap:

• Facebook: connection is valid forever if used at least once every 2 months.
• Google: connection is valid forever if used at least once every 6 months.
• Instagram: connection is valid forever if used at least once every 2 months.
• LinkedIn: connection is valid for 1 year. After that, users need to reconnect.
• Strava: connection is valid forever.
• X: connection is valid forever.

Users can manually revoke our access from within Ambassify or on the website of the 3rd party provider. Some networks will also invalidate the connection when a user changes their password.

Managers can now archive members to temporarily disable their access to Ambassify without losing member data. Archived members won't be able to log in, participate, or receive messages from Ambassify. Managers can unarchive members to restore their access to the platform.

We now offer support for customers with Enterprise SSO to automatically create, update, and delete Ambassify users based on the data in the customer's own user database (e.g., Active Directory.)

To make this work, the customer's end of the connection needs to support the SCIM protocol as well.

If you are interested in learning more about this feature, you can contact your Customer Success Manager.

We now also support sharing on Google Business. When this channel is enabled, members will be able to connect their Google Businesses to Ambassify and post updates on their Google listing straight from an Ambassify sharing campaign.

Customers who have AI features enabled will now be able to have their campaigns automatically translated from one language to another.

When you use the "Copy from another language" feature, you will be asked whether or not you want the texts to be translated.