What Qurtuba is

Qurtuba is a multi-tenant platform that runs educational organisations end to end. One deployment serves many institutions (schools, Hifz academies, or both at once). Alongside them it runs three kinds of shared platform entities, each with its own staff, sign-in and public website:

Module	Serves	Can span institutions?
Institution	A school or academy's daily work	No; each institution is its own tenant
Library	A lending library and its catalogue	Yes. One library can lend to many institutions
Store	A shop paid for from student wallets	Yes. A store can be universal or limited to chosen institutions
Fest	Arts and sports festivals	Yes. A fest can be one institution's, shared by invitation, or open to all

The people who use it

Who	Signs in at	Gets
Super admin	app.qurtuba.in	Every institution, library, store and fest; the CMS, templates, donations and the public API
Institution administrator	app.qurtuba.in	Everything in their institution, and who else may do what
Teacher / staff	app.qurtuba.in	What their role allows: their classes, attendance, marks, course tracking…
Student	app.qurtuba.in	Their dashboard: exams, attendance, achievements, library, store, notebook
Librarian	app.qurtuba.in	Their library's catalogue, circulation, members and website
Store manager	app.qurtuba.in	Their store's products, orders and storefront
Fest organiser, judge, team captain	fest.qurtuba.in	The organiser console, the judge panel, or the team panel
Visitor	any public site	Institution websites, library OPACs, storefronts, fest results

Everyone except fest staff signs in at the same place, and one person can hold several roles. See Signing in.

How the pieces fit

• One sign-in. A single account can be a teacher at one institution and a librarian at another. The platform remembers which one you're working in (your active scope), and every screen and permission follows it.
• Features, not editions. An institution's type (school, Hifz, hybrid) decides which features are on by default. Administrators can switch individual features on or off. See Institution types and features.
• Permissions everywhere. Roles grant permissions page by page (view, add, edit, delete, and more), limited to all records, assigned records or own records. The database enforces them, not just the menu. See Roles and access.
• Public by design, private by default. Anything a visitor sees is published on purpose: a website, a catalogue, a storefront, fest results. Nothing else is reachable without signing in.

Where to go next

• Setting up a new institution: Setting up an institution
• Running a library or a store: Library, Store
• Running a festival: Fest
• Building on the platform: Developers