{"id":48124,"date":"2024-06-10T12:41:32","date_gmt":"2024-06-10T11:41:32","guid":{"rendered":"https:\/\/churchtools.academy\/help\/non-knowledgebase\/uncategorized\/form-the-admin-team\/"},"modified":"2026-02-12T11:11:15","modified_gmt":"2026-02-12T10:11:15","password":"","slug":"form-the-admin-team","status":"publish","type":"docs","link":"https:\/\/churchtools.academy\/en\/help\/administration\/first-steps\/form-the-admin-team\/","title":{"rendered":"Form the admin team"},"content":{"rendered":"\n<p>Establishing ChurchTools in your congregation can simplify processes and clarify procedures. However, a certain amount of preparation is required before your congregation can use the new tool efficiently. In order for the introduction to succeed, it is particularly important to set up a good admin team.  <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is an admin team?<\/h2>\n\n\n\n<p>This team should ideally consist of three to five people. It is responsible for the technical introduction of your ChurchTools and is the point of contact for questions. The administrators configure the ChurchTools system to adapt it to the needs of your congregation.  <\/p>\n\n\n\n<p>However, the team also seeks understanding and acceptance in your congregation. This does not mean that the administrators have to take on all tasks. However, they should be open to questions and be in contact with the church leadership\/church council and be sure of their support.  <\/p>\n\n\n\n<aside class=\"wp-block-group ct-box ct-box-blue has-background is-vertical is-layout-flex wp-container-core-group-is-layout-002f1c27 wp-block-group-is-layout-flex\" style=\"border-radius:8px;border-left-color:#22c55e;border-left-width:0.5rem;background-color:#dcfce7;margin-top:var(--wp--preset--spacing--60);margin-bottom:var(--wp--preset--spacing--60)\">\n<p style=\"margin-top:0.5rem;margin-right:0.5rem;margin-bottom:0rem;margin-left:0.5rem\"><strong>Tip<\/strong><\/p>\n\n\n\n<p style=\"margin-top:0rem;margin-right:0.5rem;margin-bottom:0.5rem;margin-left:0.5rem\">As &#8220;creatures of habit&#8221;, people are generally skeptical of change. Changes are associated with uncertainties about the future and can be perceived as dangers and risks.<br>Admins should counter this by reducing fears and clarifying uncertainties and thus getting the people in your congregation on board. <\/p>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Admin team and church leadership<\/h2>\n\n\n\n<p>If a team member is also part of the church leadership or council, this would of course be an advantage, as it would be easier to reach agreements with the leadership.<\/p>\n\n\n\n<p>In any case, the congregation&#8217;s leadership and admin team should signal to the congregation that the introduction of ChurchTools is not a solo effort, but is happening in cooperation with the leadership. This promotes acceptance.   <\/p>\n\n\n\n<p><span style=\"font-weight: bold\">Ask for support<\/span><br>For the successful introduction of ChurchTools, it is important that the church leadership\/parish council\/parish team supports this project. If a <i>mandate<\/i> has been obtained from the parish leadership, further steps are easier to implement, as the admin team does not have to take them alone. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Create administrators group<\/h2>\n\n\n\n<p>The admin team is of course not fixed for all eternity. Changes to the team will come sooner or later. We therefore recommend that you create an <strong>administrator group<\/strong> in ChurchTools.  <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Advantages of an administrator group<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You can see at a glance who is currently working in the team. Changes in the team can be quickly mapped and recorded. <\/li>\n\n\n\n<li>Membership of the group automatically gives an administrator all the necessary rights. If someone leaves the group, they are also automatically revoked. <\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Create group<\/h3>\n\n\n\n<p>The Admin group works like any other group in ChurchTools.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the <em>Groups module<\/em>, create a new group called &#8220;Administrators&#8221;. You can select <em>Properties<\/em> as the group type.<a href=\"https:\/\/churchtools.academy\/help\/churchtools-module\/erstellen-bearbeiten\/37-wie-lege-ich-eine-neue-gruppe-an\/\" data-type=\"docs\" data-id=\"7220\">(Help: Create new group<\/a>) <\/li>\n\n\n\n<li>You can set the visibility of the group to &#8220;internal&#8221;. This way, everyone with a Login for your ChurchTools can see the group and know who their ChurchTools admins are. <\/li>\n\n\n\n<li>You add the team members to this group as participants.<\/li>\n\n\n\n<li>You determine the team leader and give this person the role of &#8220;leader&#8221;.<\/li>\n\n\n\n<li>In rights management, you give the respective roles the necessary global and group-internal rights<a href=\"https:\/\/churchtools.academy\/en\/help\/permissions-management\/basics-understanding-permissions\/21-open-or-restricted-permissions-management-what-suits-us\/\" data-type=\"docs\" data-id=\"7575\">(Help: Rights management<\/a>).  <\/li>\n<\/ol>\n\n\n\n<p><span style=\"font-weight: bold\">What rights should you assign?<\/span><br>The administrator team should be given at least all <code>Administrations (ehemals ChurchCore)<\/code> rights so that they can manage ChurchTools. As these rights are very far-reaching, you must be aware that these people can usually also see all data! <\/p>\n\n\n\n<p>Accordingly, there is no reason why administrators should not be granted all other global rights via the admin group to begin with.<\/p>\n\n\n\n<p>If a person leaves the admin team, they will be removed from this group and immediately lose all rights they had as a member of this group.<\/p>\n\n\n\n<p>You can find our recommendation for a sensible rights structure for this group in the article <a href=\"https:\/\/churchtools.academy\/en\/help\/permissions-management\/authorise-groups\/21-recommendations-on-permissions-for-administrators\/\" id=\"7563\">Authorization recommendation for the administrator team<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Next step<\/h2>\n\n\n\n<p>By forming an admin team and creating the group in ChurchTools, you have taken the first step and the real work can begin. In the next guides, we will introduce you to the next steps that you can take in your ChurchTools. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Video recommendations<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.youtube.com\/watch?v=EhylDYtWTY0\">Video: Assigning permissions sensibly<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.youtube.com\/watch?v=Y-RFE1hsJaU\">Video: First steps in the people and groups module<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.youtube.com\/watch?v=ejJNobhOsZs\">Video: Manage and contact groups<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Establishing ChurchTools in your congregation can simplify processes and clarify procedures. However, a certain amount of preparation is required before your congregation can use the new tool efficiently. In order for the introduction to succeed, it is particularly important to set up a good admin team. What is an admin team? This team should ideally [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"doc_category":[448],"doc_tag":[653],"knowledge_base":[426],"class_list":["post-48124","docs","type-docs","status-publish","hentry","doc_category-first-steps","doc_tag-content-outdated-en","knowledge_base-administration"],"pp_statuses_selecting_workflow":false,"pp_workflow_action":"current","pp_status_selection":"publish","acf":[],"year_month":"2026-04","word_count":627,"total_views":"328","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Jasper Stehmeier","author_nicename":"jstehmeier","author_url":"https:\/\/churchtools.academy\/en\/author\/jstehmeier\/"},"doc_category_info":[{"term_name":"First Steps","term_url":"https:\/\/churchtools.academy\/en\/help\/churchtools-modules\/first-steps\/"}],"doc_tag_info":[{"term_name":"Content outdated","term_url":"https:\/\/churchtools.academy\/en\/docs-tag\/content-outdated-en\/"}],"knowledge_base_info":[{"term_name":"Administration","term_url":"https:\/\/churchtools.academy\/en\/help\/administration\/","term_slug":"administration"}],"knowledge_base_slug":["administration"],"_links":{"self":[{"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/docs\/48124","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/comments?post=48124"}],"version-history":[{"count":5,"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/docs\/48124\/revisions"}],"predecessor-version":[{"id":48133,"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/docs\/48124\/revisions\/48133"}],"wp:attachment":[{"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/media?parent=48124"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/doc_category?post=48124"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/doc_tag?post=48124"},{"taxonomy":"knowledge_base","embeddable":true,"href":"https:\/\/churchtools.academy\/en\/wp-json\/wp\/v2\/knowledge_base?post=48124"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}