Charalampos Haris Matthaiou

It is a bit weird that you need time for a feature that was already implemented not too long ago. 
If there is no specific timeline for rollout (more of a regression fix tbh)  , does it mean that it's not yet approved by PM for development?
If so, this should be openly communicated so we do not wait for it any time soon and look for alternative workflows.
 

Anyone has a smart way to display this across all brands and languages?

With Guide Templating V2, you'll need to import a jQuery library if you want to use jQuery statements in a theme in place of vanilla JavaScript . So 

So you need to add something like this to your document_head.hbs

Hi Caroline,

Thank you for the update. I am really happy that there is progress with this implementation.
Our Zendesk instance is eagerly waiting for this rollout and finally harden our security.
Is there a way we can participate in the early rollout when its available?

After a year , there's still no update on the support of MS Stream (on Sharepoint).
Care to share any update or any possible future roadmap on that functionality?

Zendesk offers the possibility to have separate SAML configurations, one for team members (agents) and another for end users.

We would assume that each configuration should strictly authenticate users based on their SAML configuration -however this is not the case: If the same agent, is present on both IdPs, for team members and end-users, if they can sign in as end-user they can get logged in as an agent. This is wrong and raises security concerns. Zendesk should ensure that agent authentication is only permitted through the designated Agent SAML SSO setup. 

Currently Zendesk does not honor the authentication method to validate agent's entry point. The reason is that although a separate SSO was introduced, the email is still the only key for identifying the user and totally ignores the IdP source.

In our system, we want end users to sign in with a simple IdP , while agents need to sign in with MFA.
That is not possible with current authentication logic of Zendesk, as agents can totally bypass the MFA by simply log-in from end user SSO.

Do you see the problem here?

Regards,

Haris

Can Zendesk team inform us how they suggest to have localized email template?

• Dynamic Content is not working in email template.
• Liquid Markup targeting user language is not working in email template.
• Liquid Markup targeting ticket language does not work in email template.
• Brands are not the way to go. Implementing Brands just for this is not a solution.

While search works fine (across all brands), the Knowledge context panel in Support is seriously crippled in function for direct article creation due to the fact that the agent will only see templates related to that ticket's brands. This is flawed design and there doesn't seem to be a workaround for this.

This is forcing us to stay with Knowledge Capture app which is far from ideal but at least it supports templates from all brands. We really want to switch to context panel solution and utilize additional functionality, but this very important functionality is missing. Please consider adding the obvious.

Also, a minor wish on that Context Panel: Would be important to see which brand does an article belong to without opening the article.

Seriously guys? A simple tooltip hovering request for the bare minimum UX! Is that too much to ask after almost 3 years on no solution whatsoever?