Maximilian

+1 from a inbound. The use case here is again support staff impersonating users on an application. Having user consent would be ideal, but not mandatory. However audit log must...

+1 inbound. The use case is support staff impersonating users to help them resolve issues.

Workaround: Change login texts https:///ui/console/instance?id=logintexts loginNamePlaceholder: "Login with email or phone number" loginNameLabel: "Login to "

@doncicuto that's right, showing all options would be the most helpful to understand what's possible. Would it be possible to show the actual domain? I realize this gets a bit...

> Thanks for sharing this. I have not yet been able to reproduce this 😓 > > Can anybody with android give this a spin and see if NFC as...

The broad strokes are there, but it lacks imo a bit of meat on the bone. When I want to integrate my app with ZITADEL e2e, we need also to...

Agree with consistency. You were proposing a while back to stick to the Google Style guide, which I thought as the standard for now, as it is also in the...

+1 from inbound - AWS - Google Workspace - Office 365

+1 from inbound. Provisioning basic user info from ZITADEL to EntraID (users require access to Teams / O365)

This topic came up in several discussions: - Impersonation: https://github.com/zitadel/zitadel/discussions/6006 - Magic links: https://github.com/zitadel/zitadel/discussions/2075