> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notesglider.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

# Quickstart

## SECTION 1 — EXECUTIVE SUMMARY

Notesglider is a subscription-based SaaS web application built exclusively for educators. It automates the end-to-end lifecycle of academic document production — from raw structured content creation through branded PDF generation, presentation slide decks, and interactive mind maps — eliminating the manual formatting, version control, and file management burden educators currently face.

The product operates through a **three-sided, hierarchically governed platform model**:

* **Super Admin (Platform Owner)** operates at the system root level — above all tenants. They spawn and authorize Editors, approve incoming Teacher Organisations, and assign each Organisation to a specific Editor. The Super Admin has system-wide visibility and governance authority.
* **Editors (Tenant Managers)** manage the quality gate between raw Teacher content and final branded PDF output. Each Editor oversees one or more Teacher Organisations assigned to them by the Super Admin and runs the PDF generation pipeline on behalf of their Teachers.
* **Educators (Teachers)** use a clean, powerful block-based editor to author structured daily newsletters, which the system automatically repurposes into weekly compilations, monthly magazines, quarterly collections, bi-annual compendiums, annual yearbooks, PPTX slide decks for live classes, and mind maps. Each Teacher creates and administers their own Organisation (tenant unit) and manages a team of sub-members beneath them.

The core value proposition is speed, structure, and automation: a Teacher creates content once and the platform produces multiple output formats automatically, with quality assurance enforced through the Editor's review pipeline and governed by the Super Admin at the platform level.

***

## SECTION 2 — PRODUCT VISION & PROBLEM STATEMENT

### 2.1 Educator Pain Points (Solved by Notesglider)

| Pain Point                                                            | Notesglider Solution                                           |
| --------------------------------------------------------------------- | -------------------------------------------------------------- |
| Time-consuming document formatting across multiple platforms          | Single-input, multi-output automated pipeline                  |
| Difficulty organising daily content updates consistently              | Structured block editor enforces consistent document hierarchy |
| Need for both detailed notes and presentation slides from same source | One document source auto-generates PPTX, PDF, and Mindmap      |
| Manual file management and version control across formats             | Automated Drive sync, version tracking, and archival           |

### 2.2 Student Pain Points (Solved Indirectly)

| Student Pain Point                      | How Notesglider Resolves It                                       |
| --------------------------------------- | ----------------------------------------------------------------- |
| Students wait for notes/documents       | Timely, automated handout delivery                                |
| Revision backlog                        | Structured weekly and monthly compilations keep students on track |
| Content lacks structure and readability | Engaging, structured, consistently formatted output documents     |
| Manual self-note handling               | Hands-free automated notes from educator's single input           |
| No automation                           | End-to-end full automation of the document pipeline               |
| No efficient workflow                   | Streamlined, one-click generation process                         |

### 2.3 Core Product Principles

* **Educators author; the platform produces.** The Teacher's job ends when they hit "Send to Editor." Everything after is automated or Editor-managed.
* **Quality is gated, not assumed.** Every document passes through an Editor review checkpoint before reaching final PDF output. The 2-hour SLA auto-continuation ensures continuity even when the Editor is unavailable.
* **PDF and Mindmap generation are abstracted from Teachers entirely.** Teachers never interact with or even see the PDF pipeline. It is a backend concern owned by the Editor.
* **The platform is multi-tenant.** Multiple independent Editors operate their own pools of Teachers, each with full data isolation.