Does not really demonstrate "Bill" example.

[kbumsik]

Hi,

I came across this demo from a Discord chat and B2B scenario documentation.

Let's see a diagram from the doc:

B2B scenario documentation

I was told that "Bill" can be authorized in multiple orgs. But this demo does not really show "Bill" user.

[mffap]

Thanks for pointing that out.

I think we could and actually should show an external user grant. Maybe @rajatcing or @matiasracedo could have a look.

[rajatcing]

I will update the diagram, thanks for pointing out @kbumsik

[rajatcing]

cc @mffap @kbumsik please let me know and I will raise a PR.

[matiasracedo]

cc @mffap @kbumsik please let me know and I will raise a PR.

The original diagram correctly reflects how authorizations (also called user grants) work, there is no need to update the diagram.

What @kbumsik pointed out is the fact that this B2B sample application does not showcase the "Bill" user example. But that is because this is a demo showcasing how you can use ZITADEL in a B2B (Business-to-Business) context, where a company (Octagon in the image, Demo-Vendor in this sample app) is providing a customer portal to their customers (Pentagon in the image, Demo-Customer in this sample app).

This sample B2B application was not intended for managing internal users from the Vendor (granting) organization. We can extend the functionality to also showcase that, which would be mimicking exactly what the Zitadel Console does. We will discuss internally and come to a decision.

I think we could and actually should show an external user grant

This, on the other hand, we can do more easily. I will extend the example to include this and update the readme, thanks for pointing that out.