Multi-tenant sign-in

[nmwur]

• v1 for email

• v2 for completing web3 modalities

[nmwur]

• google and discord auth - https://github.com/nmwur/app-nesting/commit/bea789d29335a8dfc381f030be8d68f62ac2109a
• web3 wallet connection - https://github.com/nmwur/app-nesting/commit/73a64e3b014a9577ec4b2540f65ff71912758738

[nmwur]

next:

• have different organizations visible to different users

[nmwur]

mocked the invites ui:

• 

• 

• 

[RichardJamesLopez]

Awesome.

mocked the invites ui:

Just to clarify if user (specifically Inviter) sets max number of users to 25, then that means that up to 25 different logins can be created and have access to the Members list?

[nmwur]

yes

[RichardJamesLopez]

Adding specific sub-tasks as per the Figma file:

• [ ] Test different users with different API access (NOT different DB access; separate issue)
• [ ] Create a separate “Customer” that has access to a different set of APIs
• [ ] Test transfer of user from Admin to Member (by accident). Can the remaining or newly assigned Admin turn me (currently Member) back to admin
• [ ] requirement for an admin or owner at anyone time

[nmwur]

1.

Test different users with different API access (NOT different DB access; separate issue) Create a separate “Customer” that has access to a different set of APIs

can a Customer have more than one api access (e.g. to two notion tables and one hubspot table)?

---

2.

Test transfer of user from Admin to Member (by accident). Can the remaining or newly assigned Admin turn me (currently Member) back to admin

should only the higher roles be able to manage the lower roles? for example, a user could be transferred from/to Admin only by the Owner and not by another Admin. that's how discord handles it, should we do it similarly?

[RichardJamesLopez]

should only the higher roles be able to manage the lower roles? for example, a user could be transferred from/to Admin only by the Owner and not by another Admin. that's how discord handles it, should we do it similarly?

Yes, let's default to this.

[RichardJamesLopez]

Test different users with different API access (NOT different DB access; separate issue) Create a separate “Customer” that has access to a different set of APIs

can a Customer have more than one api access (e.g. to two notion tables and one hubspot table)?

Looks like we are discussing the same phenonomen here: https://github.com/users/RichardJamesLopez/projects/1?pane=issue&itemId=64163141

I think a customer having access to more than 1 type of API access is a good solution, but I think we need to outline the pros/cons of whether we should or shouldn't do that.

[nmwur]

true, i think we could narrow this task down to:

• sign-in via google
• role-based user management
  • promote/demote admins
  • kick members
• invites (except #28)

the items above seem to be done: