Sharing what my understanding of Userverse currently is

[Thwani47]

In the project's main readme, Userverse is described as A multi-tenant user and organization management platform. Out of the box, it offers

• User and org registration flows
• RBAC
• Multi-tenancy support
• Flexible APIs for integrating your SaaS or internal tools

From this, this is what I understand

Userverse is a (multi-tenant) platform one can use to manage users and their organization(s)?*.  
We can use Userverse to register users, manage user sessions, user credentials, etc. 
We can assign users access to certain resources in an organization based on their role (RBAC). 
We can easily integrate other SaaS(?) and internal tools with Userverse.

Some questions/concerns

1. Multi-tenancy from the start

I somewhat see what benefits consumers would get if we provided a multi-tenant platform from the start. However, I strongly believe we're adding too much complexity to the project before it can even have legs. I suggest we have a working single-tenant solution that we can get out to users, and work on a multi-tenant solution we can provide once we have a working solution. I am happy to discuss this further.

2. The idea of organization management

I am failing to understand what organization management refers to. I understand the user management part. Does the organization management refer to us enabling consumers being able to model some parts of their organization (this could be IT infrastructure, internal tools, SaaS applications, etc) inside Userverse and being able to control access, integrations, etc?

3. Proposed plan for building the frontend

Can we discuss what the frontend for Userverse (I'm assuming it's the UI portal) is supposed to expose to the user before we can suggest the tool stack?

[Skhendle]

Thanks for the feedback, @Thwani47 – really appreciate the thoughtful input.

Multi-tenancy: You're right that starting with multi-tenancy adds complexity early on. That said, the current setup already supports company creation by any user – something we can easily restrict to superusers. This allows us to implement and validate core features like RBAC within a single company context, which will scale naturally when we revisit multi-tenancy more intentionally.

Organization management: By “organization,” I’m referring to companies linked to external identity providers like GitHub, Google Auth, or Keycloak. This gives us a foundation for integrating with tools or systems where SSO and external identity management are required.

Frontend plan: I’ve shared a proposal here: https://github.com/orgs/SoftwareVerse/discussions/45. Let’s use that thread to align on what the UI should expose before settling on the stack.

Happy to discuss any of this further