yogsototh/deft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

notes/customer_manager.org

Browse source
This commit is contained in:
Yann Esposito (Yogsototh) 2021-10-15 16:14:43 +02:00
parent 24ed834d07
commit 8dee1e141c
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646
1 changed files with 3 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
notes/customer_manager.org
View file

@ -31,13 +31,10 @@ enough to determine who is the customer that a user identity belongs to.
It doesn't look like we will stop supporting non 3rd party IdP login? It doesn't look like we will stop supporting non 3rd party IdP login?
So it means the we already have a design-space complexity. The consequence for the delivery is that it could make the situation quite
difficult because we will need to have different behaviors depending on
this for every user identity.
If the User Identity is linked to a Customer or not.
Without 3rd party IdP login we could imagine a user could belong to
multiple Customers. I think we should assume, for sake of simplicity that
this should not be the case, and our customer control access to their
platform via providing (or not) an email using their own domain name.
** Quick wins along the way ** Quick wins along the way
*** Local Account Switch (Tenancy Switching) *** Local Account Switch (Tenancy Switching)