Members & Invitations

This section explains how to manage:

Who can join your school
How invitations work
How members are managed
How access can be restricted or revoked

Membership structure is one of the most important governance layers in your school.

Membership Model in Hischool

Schools operate under one of two access models.

Discoverable Schools

Any registered user can find and join the school.
No approval process is required.
New members receive the default role automatically when they join.

Best suited for open communities or public learning environments.

Invite-Only Schools

Users must join through:
- an invite link
- an invite code
Only authorized roles can generate or manage invitations.
There is no manual approval queue.

Best suited for private institutions, classes, or structured programs.

Member Lifecycle

Each member follows a general lifecycle inside a school:

Invited or joined the school
Assigned a role
Participates in groups and activities
May be removed or banned if necessary

Administrators are responsible for maintaining a healthy and organized membership structure.

Inviting Members

Users with appropriate permissions can:

Generate invite links
Create invite codes
Share invitations with potential members
Revoke or disable active invitations

See: → Invite Members
→ Manage Invitations

Managing Active Members

Administrators can manage existing members by:

Changing member roles
Modifying school-specific identity (if enabled)
Removing members from the school
Banning members when necessary

See: → Change Member Identity
→ Kick Members
→ Ban Members

Roles and Default Permissions

When a member joins a school:

They are assigned a default role.
Permissions depend on that role.
The assigned role determines what the member can see and do.

See: → Roles & Permissions

Discoverability and Invitations

Even if your school is discoverable:

You can still use invite links for direct onboarding.
You can configure the default role for newly joined members.
Private groups inside the school can remain restricted.

Discoverability does not override internal role permissions.

Best Practices for Member Governance

Before inviting large numbers of members:

Define your role hierarchy.
Configure default permissions carefully.
Restrict group creation if necessary.
Clearly communicate school policies.

A well-defined structure helps prevent long-term moderation issues.

When to Remove vs Ban

Remove (Kick)

The member is removed from the school.
They may rejoin later if the school is discoverable or if they receive a new invitation.

Ban

The member is restricted from joining the school again.
They cannot rejoin unless they are manually unbanned.

Use bans only when necessary.

See: → Banned Users

Administrative Responsibility

Managing members is not only about controlling access — it is also about:

Protecting the learning environment
Encouraging respectful collaboration
Maintaining institutional standards
Enforcing school policies

Clear governance improves long-term community stability.