Cloud document storage with KIDUART
Schools accumulate documents: birth certificates, transfer certificates, mark sheets, staff qualifications, ID proofs. KIDUART stores uploads in managed cloud storage Cloudinary for media and Amazon S3 with CDN delivery for documents and links each file to the record it belongs to, so a document is found from the student's profile rather than a folder someone renamed.
What you get
- Documents attached to the student or staff record
- No shared drive naming conventions to maintain
- Access follows the same role permissions as the record
- Files delivered over CDN, so a large certificate opens quickly
- Uploads available from the panel where the work happens
The connection, hop by hop
How Cloud document storage actually works here
No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.
Upload at the record
The front office attaches a document while admitting a student or onboarding a staff member.
Scanned and stored
The file is checked and written to managed cloud storage rather than an email attachment or a shared folder.
Linked to the profile
The document is attached to that student or staff record with its type, so it is searchable by person.
Opened by permission
Only roles with rights on that record can open it, and access follows the same rules as the record itself.
Keys, data and the bill
Who holds the credentials
Managed by KIDUART as part of the platform, so your school does not run buckets or CDNs.
Where the data sits
Your documents belong to your school and are exportable when you ask.
Who gets billed
Storage is part of your subscription. There is no separate cloud bill to reconcile.
Where it lands in the product
The modules this integration writes into
An integration is only useful if it writes into the module your staff already work in. These are the exact modules involved.
Setup, step by step
Connecting Cloud document storage
Confirm the document types you collect during onboarding
We map each type to the record it attaches to
Bulk import your existing admission documents
Set which roles may view each document type
Train the front office to upload at admission time
What you need on your side
- The document checklist your school actually collects
- Existing files in a readable folder structure for bulk import
- A decision on which staff roles may view them
Questions schools ask
Cloud document storage, answered plainly
Who can see a student's documents?
Only roles with permission on that record. A class teacher does not automatically get a student's financial or identity documents.
Can we bulk upload existing files?
Yes, bulk import is part of onboarding. The cleaner your existing naming is, the faster that mapping goes.
Also in files, data and developer access
Related integrations
Excel and CSV exports
Take any list or report out as Excel, CSV or PDF for your accountant, trust office or board submission.
REST API and webhooks
Build against a versioned REST API with managed API keys, published reference docs and rate limits.
Portal usage analytics
Planned: adoption analytics for the parent and student portals, built without profiling children.
See Cloud document storage in a live demo
We will run the connection on screen with your own scenario your fee book, your parent groups, your school accounts.
30-minute walkthrough
Booked around your school hours
Run on your own data
Your fee heads, classes and staff roles
No card, no lock-in
Nothing is charged to see the product