Kindergarten Parent Portal: From Chaos to Order

Imagine: parents call 20 times a day — "What's for lunch today?", "When are the photos from the matinee?", "Can I bring my child later?" Administration spends hours on paper announcements, and photo albums exist only in WhatsApp, where they get lost. We build a unified portal that solves these problems: news, menu, records and photos — all in one secure place. After implementation, the number of repeat calls drops by 70%, and parent engagement triples. Paper and printing costs go to zero.

Features of the Kindergarten Portal

The public part is the kindergarten's storefront. Homepage: photos of the interior and playground, age groups, daily schedule, format (full day or short stay). "Teachers" section with photo, name, education, experience — critical for trust. Curriculum: methodologies (Montessori, developmental), class schedule, extracurricular activities. Meals: weekly menu updated by the admin via a dashboard — PDF upload or table. News and photo albums: events, holidays, excursions. Children's photos — only in the private parent dashboard, not publicly accessible.

How the Parent Personal Account Works

The personal account is an engagement tool. News and announcements for their group, photos (private access — only their child or the whole group, configurable), weekly menu, class and event schedule, notifications about certificate readiness, absence notes (no need to call). Authorization: email + password or via ESIA for state kindergartens. Online queue enrollment: application with child's details, desired start date, and contacts. For municipal kindergartens — integration with the Gosuslugi portal or regional queue system.

Why a Portal is More Efficient than Paper

The numbers speak for themselves: a portal saves up to 40 hours of administrator work per month and reduces teacher workload by 30%.

How We Ensure Data Protection

Federal Law No. 152-FZ on Personal Data requires parental consent for processing personal data. We implement consent collection in the personal account, as well as the ability to revoke it. Children's photos are never published without signed consent — all media is hidden behind authorization. Server infrastructure is hosted in Russian Federation data centers with certified encryption. All transactions are logged, and access is strictly segregated.

Setting Up a Private Photo Album: Step-by-Step

1. In the admin panel, create a gallery and upload photos.
2. In gallery settings, select access type "parents only."
3. Choose whether to show images of the whole group or only their child.
4. Publish the gallery — parents will see it in their personal account.
5. Parents can download photos. Administrators see view statistics.

Our Development Process

What's Included

We deliver:

• Full source code (GitLab repository with documentation)
• Hosting and admin panel access
• Complete administrator manuals
• Employee training (2 hours online or on-site)
• Warranty on hidden defects and first-year support

Timeline and Cost

Timelines — from 1 week (informational site) to 6 weeks (portal with dashboard and integrations). Cost is calculated individually after analyzing your requirements. We provide an accurate estimate before work begins.

Why Choose Us

5+ years of experience in educational portal development, 20+ successful projects, certified data protection solutions. We use stacks: React/Next.js for frontend, Laravel/Python for backend, PostgreSQL/Redis for database. All portals undergo an audit for 152-FZ compliance.

Get a consultation on your project — we will assess the scope and offer the optimal solution. Contact us to start work.

Development of Corporate Portals and Internal Systems

We specialize in developing corporate portals — CRM, ERP, LMS, and Intranet. Each project starts not with landing page layout, but with how business rules will be embedded into the architecture: who sees which data, how 1C and accounting systems sync, how 500 contacts turn into 500,000 without performance degradation. Over 7 years, we have delivered over 40 portals for companies with 50 to 5000 employees. We will evaluate your project in two business days — just contact us.

A public website can be launched without detailed design — iteratively improved based on feedback. With a corporate portal, this approach does not work: the cost of fixing architectural decisions after launch for 200 users is incomparably higher. Therefore, we spend 70% of our time on analysis and prototyping, and write code only after the role matrix and integration scheme are approved.

Three areas where bad decisions are often made: access rights model, performance on large data, and real-time updates.

How to build a role model for 30 departments?

Access rights model. "A manager sees only their own clients, a department head sees the entire department, a director sees the whole company, but financial data is visible only to the CFO and above." This is not three roles — it's a matrix of roles, permissions, organizational units, and record ownership. Implementing it with if ($user->role === 'manager') in controllers will make the code unmaintainable after six months.

The correct approach: Spatie Laravel Permission for basic role model + Policy classes for object-level permission (can('view', $deal) checks not only the role but also ownership). For complex hierarchical structures — ABAC (Attribute-Based Access Control) instead of RBAC.

Performance on large data. CRM with 500,000 contacts, filtering by 10 fields, sorting by activity — a naive implementation yields 15-second queries. Composite indexes, denormalization of aggregates (last_activity_at on the record itself instead of MAX over related table), Elasticsearch for full-text search on contacts.

Real-time updates. Multiple employees working on the same document or task. Without WebSocket — constant setInterval with polling every 5 seconds, extra server load, update delays. Laravel Broadcasting + Pusher/Soketi or a custom WebSocket server on Node.js — for notifications and real-time changes.

CRM Systems

Typical set: contacts, companies, deals, activities, sales funnel, reports. Technically straightforward. The complexity lies in the details.

Pipeline with custom stages. Every company wants its own funnel. Stages must be configurable without deployment. Table pipeline_stages with position, color, is_final, probability — and drag-and-drop for reordering on UI (React DnD or dnd-kit).

Change history. Who and when changed a deal status, reassigned a responsible person, added a note. Audit log via Observer or spatie/laravel-activitylog. On UI — timeline with filtering by activity type.

Email integration. IMAP/SMTP for connecting corporate mailbox, automatic linking of incoming emails to contacts by email address. This works reliably only with proper handling of bounces, spam, auto-replies — filtering is required.

Why is ERP not about code but about data?

ERP is when CRM, warehouse, production, accounting, and HR are unified into a single system. Full ERP from scratch is rare (usually integrating with existing systems), but modular systems for specific businesses are common.

Key principle: financial operations must be immutable. Not UPDATE orders SET status = 'cancelled' — but creating a new record order_cancellations with a reference to the original order. This is the immutable ledger principle, which simplifies auditing and reconciliation.

Integration with 1C is almost always part of an ERP project. Two-way synchronization: from 1C to portal (directories, balances, prices) and from portal to 1C (orders, documents). RabbitMQ as an event bus between systems is more reliable than direct HTTP interaction — if 1C is unavailable, messages wait in the queue.

How are LMS structured: learning platforms?

Learning Management System — courses, modules, lessons, tests, certificates, user progress.

Video content is the most demanding part of an LMS. Storing video on your own server and serving via Nginx is a bad idea: expensive, slow, no adaptive bitrate. Correct approach: upload to S3/Cloudflare R2, transcode via AWS Elemental MediaConvert or Mux, HLS playlist for adaptive streaming via Video.js or Plyr.

Viewing progress — periodic sending of watch_position from the frontend (every 10–30 seconds), storage in Redis with periodic synchronization to PostgreSQL. Do not save every second to the database — it will kill performance.

SCORM compatibility — if integration with corporate training materials is needed. Separate module, there are ready libraries (scorm-again).

Intranet and HR Portals

Corporate intranet: news, documents, organizational structure, HR processes (vacations, requests, KPIs).

Organizational structure in the database is a hierarchical structure. Adjacency list (parent_id on each record) is simple to implement but slow for recursive queries. Nested Sets or Closure Table are faster for reading hierarchies, more complex for changes. In PostgreSQL — recursive CTEs (WITH RECURSIVE) with adjacency list — a balance between simplicity and performance.

Document and request approval — workflow engine. Simple linear approvals (employee → manager → HR → accountant) can be done without a special engine. Non-linear (parallel branches, conditional transitions, delegation) — consider ready solutions: Temporal.io for workflow orchestration or a custom state machine based on the state-machine pattern.

What is included in the work

When ordering a corporate portal development, you receive:

• Architectural documentation (ER diagrams, integration scheme, role matrix)
• Full code in a Git repository with CI/CD
• Access to infrastructure (hosting, databases, storage)
• Training for administrators and key users (2–3 sessions)
• Warranty support for 3 months after launch

Our design principles rely on official Laravel documentation on authorization (Policies) and recommendations for working with queues.

Technical Stack for Portals

Timeline Estimates

The cost is calculated individually after a detailed analysis of requirements and role model. To get a preliminary estimate, contact us — we will analyze your task and offer an optimal turnkey solution.