Juhani

Hi Jazmin, Thanks! I can confirm the link now takes me directly to our Microsoft login page. This is a really interesting approach, it might even work better than the Microsoft SSO button, since most of our people are already signed into their Microsoft accounts. Ideally, the link should just take them to our workspace’s home page and create an account automatically, without them having to do anything 💪 That said, I do wonder if it might feel a bit sketchy to some that a link leads straight to a page asking for company credentials 🤔 I’ll keep an eye on how people respond to having more direct access to the platform and track any issues that might prompt us to revisit this. Really appreciate your and the team’s efforts on this!

Jazmin Thanks for the update. Unfortunately, changing our SSO name format isn’t a viable option. It’s tightly integrated across numerous systems and tweaking it for Dovetail would cause unnecessary, most likely larger, disruption elsewhere. Given the scale and complexity of our infrastructure, it’s not realistic to expect us to reconfigure our enterprise-wide identity mappings to suit a single vendor’s assumptions. A more robust solution on your end (like parsing names properly or supporting separate fields) would be far more sustainable. Could this be added to the team's backlog, please?

Hi again, Just wanted to add something, which I assume is related to SSO. When our users login to Dovetail the first time, their account name will be created as [Last name] [First name]. This can cause e.g. Chat functionality to use our last name in personalization texts. It feels a bit awkward 😅

Right on the mark Stephen! 🎯 Would love if the AI summary could "evaluate" the data, so that it could say e.g. 'People in your sales organization are struggling with A, B and C, but their managers are also concerned about D and E being issues for them'. That would clearly give me an idea of what our users are actually saying, rather than just grouping topics A-E together and of equal value

Sure, it's pretty much identical to what Paul shared above

Pam D. For us, first-hand data comes from people who actually use the tool or service. Second-hand data comes from people who talk about those users (usually in support roles). These people often have great insights, but their input is filtered through their own experiences. In interviews, support roles can give both kinds of data:

That’s why Emi F.’s idea of tagging first- and second-hand data makes sense and I'll be adopting it as well 🙏 (if I understood it right). Most of our users just want quick AI insights and designers doing research don’t usually worry about the difference between data types, they just want useful info fast. That’s why I wish there were system-level tools to automatically tell the difference, so AI search could handle it better. Then I could still tag second-hand data when I spot it 🤓

Hi Matt D., thanks for the info! I'll contact our IT team about the Entra ID connection. 'Continue with Microsoft' is relatively clear (definitely better than 'Continue with Entra ID'), but a custom text is even better! There's still the remaining question about the Password-field being available on the login screen, even though I have deselected it in the Authentication page. I would ideally like to get rid of it, so that users have only one option when they want to enter Dovetail. Is this something you can advice or should I send an email to sso-support?