What this module is for
Create notices, assign targets, manage attachments, publish/archive/restore, print notices, and use AI drafts safely.
Prerequisites
- Notice or notification permissions assigned
- Target classes/sections/students/staff available
- Attachment files safe and supported
Main screens
Step-by-step workflows
Publish a notice
- Open Message & Notifications or Notice page.
- Create a notice with title, date, content, status, and audience.
- Assign targets where required.
- Upload safe attachments only if needed.
- Publish after review.
Use AI notice draft
- Open notice form where AI is available.
- Generate a draft.
- Review and edit the draft.
- Save or publish only after human approval.
Operational detail
Permission checkpoints
- Notice create, edit, publish, archive, restore, print, attachment, template, and notification actions require communication permissions.
- Targeted notices should only reach selected classes, sections, students, staff, or all-school recipients according to the saved audience.
- AI notice drafts require both AI and notice permissions and remain draft-only until approved.
Field guidance
Use a short clear title that parents, staff, and students can recognize quickly.
Select all school, class-section, student, staff, or other supported recipient groups carefully before publishing.
Use the school date format in rendered views and print outputs.
Attach only safe supported files and avoid private document numbers or unnecessary personal information.
Keep draft notices unpublished until reviewed. Archive old notices instead of deleting useful communication history.
Use templates for repeated messages such as reminders, events, announcements, and follow-ups.
Validation and system feedback
- Notice save validates required title, content, date, status, audience, and attachment rules.
- Publish and archive are lifecycle actions and must match the current notice state.
- Recipient scope is validated server-side before notifications are sent or shown.
- AI-generated notices cannot publish themselves.
Common mistakes to avoid
- Publishing to all school when only one class should receive the notice.
- Uploading private files into public or parent-visible notices.
- Using draft AI text without editing tone and facts.
- Deleting notices that should be archived for history.
Recommended next steps
Screenshot plan
Final public screenshots will use synthetic QA data only. Sensitive values such as names, phone numbers, emails, admission numbers, document numbers, credentials, cookies, tokens, and internal IDs must be removed or redacted.
Important safety notes
Use normal Schoolixa workflows
Public docs explain user workflows only. They do not expose internal IDs, direct database operations, credentials, provider prompts, or private system configuration. Permission visibility in the interface does not replace server-side permission checks.