Skip to documentation content
Schoolixa Documentation
Campus Operations

Notices & Communication

Create notices, assign targets, manage attachments, publish/archive/restore, print notices, and use AI drafts safely.

Audience
Admins, office staff, teachers, and communication managers
Last reviewed
September 2, 2026

Overview

Create notices, assign targets, manage attachments, publish/archive/restore, print notices, and use AI drafts safely.

Before you start

  • Notice or notification permissions assigned
  • Target classes/sections/students/staff available
  • Attachment files safe and supported

Main screens

Notices Notice Form Target Assignment Attachments Print Bulk Templates Notification Logs

Step-by-step workflows

1

Publish a notice

  1. Open Message & Notifications or Notice page.
  2. Create a notice with title, date, content, status, and audience.
  3. Assign targets where required.
  4. Upload safe attachments only if needed.
  5. Publish after review.
2

Use AI notice draft

  1. Open notice form where AI is available.
  2. Generate a draft.
  3. Review and edit the draft.
  4. Save or publish only after human approval.

Operational detail

Permission requirements

  • 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.

Notice title

Use a short clear title that parents, staff, and students can recognize quickly.

Audience

Select all school, class-section, student, staff, or other supported recipient groups carefully before publishing.

Notice date

Use the school date format in rendered views and print outputs.

Attachments

Attach only safe supported files and avoid private document numbers or unnecessary personal information.

Publish state

Keep draft notices unpublished until reviewed. Archive old notices instead of deleting useful communication history.

Templates

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.

Safe use

Keep documentation and support privacy-safe

These guides explain normal user workflows only. Do not share passwords, OTPs, tokens, cookies, private student identifiers, payment details, raw internal IDs, provider configuration, or stack traces in support messages or screenshots.

  • 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.
  • Draft notice
  • Assign audience
  • Review attachments
  • Publish or archive