[Planing]: Authentication, Authorization, Profile

[HMarzban]

Feature Overview

We aim to build a multi-tenant, user-centric documentation platform focusing on privacy, personalization, and ease of use. Each user will have their own unique subdomain and can create public or private documents under their namespace. Additionally, for unregistered users, we will provide an anonymous auth system that allows them to create documents in a free version, which can be migrated to their subdomain upon registration.

Implementation Steps

1. Authentication and Authorization

We will use the Supabase Auth service to handle authentication and authorization. Supabase provides a robust and secure auth system that supports both third-party and custom auth providers.

Tasks:

• Integrate Supabase Auth into our Next.js application
• Implement sign up and login functionality
• Implement session management for logged-in users

2. User Subdomains and Namespace

When a user signs up, we will ask for a unique namespace that will be used for their subdomain. All user activities will then be associated with this namespace.

Tasks:

• Update user sign up form to include namespace input
• Implement server-side validation to ensure namespace uniqueness
• Configure our DNS to support wildcard subdomains

3. User Dashboard and Document Management

Each user will have a dashboard where they can manage their documents. They can set documents as private or public, and manage other document metadata.

Tasks:

• Design and implement user dashboard UI
• Implement document management features (create, update, delete, set visibility)

4. Anonymous Auth and Document Migration

For users who have not signed up, we will implement an anonymous auth system that allows them to create and manage documents. If they decide to sign up, the documents created in the free version will be migrated to their subdomain.

Tasks:

• Implement an anonymous auth system
• Design and implement document migration process

This is a high-level plan, and individual tasks may need to be broken down further. Each step should be followed by a review and testing phase to ensure we're building things right and building the right things. We also need to consider infrastructure requirements, potential scalability issues, and of course, security at every step of the way.

[HMarzban]

@edsaperia and I have deliberated on the subject of user profile and authentication features, along with related functionalities. Our aim is to increase customization and interaction between our product and its users. This is the recap list of our outcomes discussion.

1. User Authentication: Login will be facilitated through Google Single Sign-On (SSO) or through email magic links for secure authentication.
2. Mandatory Login: To ensure data security and integrity, users will be required to log in before they can edit content or engage in chats. If a user attempts to edit or chat without being logged in, a login modal will a
3. Custom Subdomains: Users will have the option to pay for custom subdomains. This allows for personalization and can strengthen their brand or personal identity within the platform.
4. User Interface Simplicity: To maximize user convenience and experience, all functions, including authentication, profile management, and document editing, will be accessible directly from the homepage or within document pages. This will reduce navigation complexity and improve usability.