Skip to content

School Management

The School Management section is designed for users responsible for running and governing a school within Hischool.

This typically includes:

  • School Owners
  • Administrators
  • Moderators
  • Educators managing structured communities

If you are a regular member and not responsible for administration, see:

Schools & Groups


Managing a school in Hischool means controlling how the community operates.

This includes deciding:

  • Who can join the school
  • What members are allowed to do
  • How groups are structured
  • How content is moderated
  • How long data is retained
  • Who has administrative authority

Schools in Hischool are structured communities, not just chat spaces.
They require clear organization, permissions, and governance.


Schools can operate in two primary access modes.

  • Any registered user can join the school.
  • No approval process is required.
  • Membership is open by default.

This model works well for public communities or open learning environments.


  • Members must be invited to join.
  • Access requires an invite link or invite code.
  • Only authorized administrators can send invitations.

This model is suitable for private organizations, classrooms, or internal communities.

There is no manual approval queue.
Access is controlled through discoverability settings and invitation mechanisms.


School management in Hischool is organized into six core areas.


Configure how your school appears and operates.

This includes:

  • Creating a school
  • Configuring general settings
  • Customizing appearance
  • Managing verification
  • Applying advanced configuration options

These settings define your school’s identity and visibility.


Control who can join and remain in your school.

This includes:

  • Inviting members
  • Managing invite links or codes
  • Updating member identity (if permitted)
  • Removing members
  • Banning members

Membership is managed through discoverability settings or invitation systems.


Define authority and responsibilities within your school.

This includes:

  • Creating roles
  • Editing permission rules
  • Assigning roles to members
  • Managing access levels
  • Configuring permission policies

Roles determine what members can see and what actions they can perform.

This is the foundation of structured governance.


Organize collaboration and communication within your school.

This includes:

  • Creating groups
  • Structuring categories
  • Configuring group privacy
  • Managing access within groups

Groups define how members interact on a daily basis.


Maintain a safe, respectful, and productive environment.

This includes:

  • Managing banned users
  • Reviewing reported content
  • Enforcing school policies

Effective moderation helps ensure healthy collaboration and community standards.


Manage long-term administration and system-level operations.

This includes:

  • System messages and activity logs
  • Data retention policies
  • Backup and restore (if available)
  • Deleting a school
  • Transferring ownership

These actions affect the entire lifecycle of the school.


Each school has exactly one Owner.

The Owner:

  • Has full control over the school
  • Can transfer ownership
  • Can delete the school
  • Has ultimate authority over configuration

Administrators can:

  • Manage members
  • Configure roles and permissions
  • Moderate content
  • Maintain school structure

However, administrators cannot delete the school or transfer ownership unless explicitly permitted.

Understanding this hierarchy is important for maintaining stable governance.


Before configuring your school, consider the following:

  • Should the school be discoverable or invite-only?
  • What roles are required?
  • Who should have moderation authority?
  • How should groups and categories be structured?
  • What content policies should apply?

Planning your structure early helps prevent long-term management issues.