DASHIFY is being designed so the right people can manage the right work without every user needing the same screens or access.
Illustrative product concept · DASHIFY by BRIZNOVAThese visuals describe the proposed experience and working approach. Final screens, permissions and available features will be confirmed as the product is built and validated with schools.
These are intended role journeys. Final permissions and workflows will be designed with each pilot school and reviewed before live use.
Oversee the school’s operating structure and review information relevant to day-to-day management.
Complete recurring classroom tasks through a focused workflow that avoids unnecessary administration.
Keep fee configuration, collection entries and follow-up records organised and reviewable.
Parent and student self-service is a possible later phase, subject to school requirements and privacy controls.
Access should follow responsibility.
A class teacher does not need the same access as an accounts administrator. A parent should not be able to browse another family’s information. Permission design must reflect the school’s real responsibilities.
DASHIFY’s planned access model includes role-based permissions, separation of school workspaces and reviewable administrative actions. These controls must be implemented and tested before live student information is introduced.
We can walk through your current process and identify which roles, permissions and everyday tasks should shape a first pilot.