Ensure that this isn’t caused by browser addons that may fish away parts of the UI.
If that’s not the case, you may want to have a look at the configuration of your default signup role.
Thanks. Indeed we fixed at least the LDAP login by properly configuring LDAP roles. Now with SAML there’s possibly something else we need to figure out with the login username.
Please cross check the users permission in question.
If this is an existing user (in theory), please ensure that you’re providing Zammad the SAML attribute it’s expecting based on our documentation.
Above described behavior looks like permission issues and, if existing user, wrong attribute usage.