Need help with hitobito?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

217 Stars 67 Forks GNU Affero General Public License v3.0 5.2K Commits 191 Opened issues


A web application to manage complex group hierarchies with members, events and a lot more.

Services available


Need anything else?

Contributors list

hitobito logo

Welcome to hitobito 人人

hitobito is an open source web application to manage organisation and communities with complex group hierarchies with members, events, courses, mailings, communication and a lot more.

Maintenance Documentation Status GitHub Open Source Helpers Build Status


Check out our development kit

More detailed development documentation can be found in doc/development.

This is where you also find some Deployment Instructions.


The architecture documentation in German can be found in doc/architecture.

Two topics shall be mentioned here explicitly:

Group Hierarchy

hitobito provides a powerful meta-model to describe group structures. Groups are always of a specific type and are arranged in a tree. Each group type may have several different role types.

This core part of hitobito does not provide any specific group or role types. They have to be defined in a separate plugin, specific to your organization structure.

An example group type definition might look like this:

class Group::Layer < Group
  self.layer = true

children Group::Layer, Group::Board, Group::Basic

class Role < Leader self.permissions = [:layer_full, :contact_data] end

class Member < Role self.permissions = [:group_read] end

roles Leader, Member end

A group type always inherits from the class

. It may be a layer, which defines a set of groups that are in a common permission range. All subgroups of a layer group belong to this range unless a subgroup is a layer itself.

Then all possible child types of the group are listed. When creating subgroups, only these types will be allowed. As shown, types may be organized recursively.

For the ease of maintainability, role types may be defined directly in the group type. Each role type has a set of permissions. They are general indications of what and where. All specific abilities of a user are derived from the role permissions she has in her different groups.

See Gruppen- und Rollentypen for more details and hitobito_generic for a complete example group structure.

Plugin architecture

hitobito is built on the plugin framework Wagons. With Wagons, arbitrary features and extensions may be created for hitobito. As mentioned above, as there are no group types coming from hitobito itself, at least one wagon is required to define group types in order to use hitobito.

See Wagon Guidelines or Wagons for more information on wagons and its available rake tasks.


You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can. Before opening any pull request or issue, please search for existing issues (open and closed) and read the contributing guidelines. If you are part of an organisation that uses hitobito, please discuss your intent with the responsible person of your organisation.


hitobito made with 💙 and the incredible community:

  • Jungwacht Blauring Schweiz
  • Puzzle ITC GmbH
  • Pfadibewegung Schweiz
  • hitobito AG
  • CEVI Regionalverband ZH-SH-GL / CEVI Schweiz
  • Dachverband Schweizer Jugendparlamente DSJ
  • Insieme Schweiz
  • Forschungstelle Digitale Nachhaltigkeit
  • CH Open
  • Digital Impact Network
  • Schweizer Blasmusikverband
  • GLP
  • Die Mitte
  • Stiftung für junge Auslandschweizer

Please contact KunoKunz if you want to be part of our community.


hitobito is released under the GNU Affero General Public License.

The hitobito logo is a registered trademark of hitobito LTD, Switzerland.

btw: hitobito 人人 means "everyone"

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.