Organisation Level Roles
GoDoChurch gives you the ability to connect multiple churches into what we call an organisation. Doing so allows churches to share useful information and to coordinate their administration. Furthermore, multiple organisations can be connected into what we call a family, allowing a movement of churches to be structured into clusters or regions while being connected on a national level.
One of the added features churches get when they are connected into an organisation or family, is they are able to specify a set of church roles that will show in each of their connected databases. A church role is a position in a church that is not a ministry, but which you still want to keep track of. Some examples include: pastor, elder, deacon, board-member, admin staff, etc. When an organisation creates organisation level roles it a) makes those roles visible in each connected database, allowing local administrators to say who fills those roles in their specific church. This, in turn, allows the administrator who oversees the organisation to draw a report of ALL the pastors, deacons, admin staff (or whatever org level roles are set) from ALL the connected churches, and to use those lists for communication purposes. This can be tremendously useful for regional communication.
How do you create organisation level roles?
Org level roles are created and managed from the database that functions as the org level database for a collection of churches. You can read all about how to connect churches into an organisation in Connecting multiple churches into an organisation or family.
If org level roles are set, will a local church be able to have their own custom roles?
Yes. Setting org level roles does not force a local church to use only those roles. A church will still be able to set up their own custom church roles. That being said, the whole purpose of org level roles is that they are used by each local church in the organisation so that this info can become available at a regional level. Importantly, only the information contained in org level roles will be available at an organisational level. The info stored in custom roles is only visible in the database that created those custom roles.
How will local churches be able to differentiate between an org level role and a custom role?
The moment org level roles are set, a new set of buttons appears in the Church Roles module of all local databases that allows users to view either custom church roles or roles set by the organisation. If no org level roles are set then local churches will only see their own custom roles.
Creating organisation level roles
Note: Only someone with org level permissions will be able to create and edit these roles.
To create org level roles:
Sign into the database that is set up to manage your organisation.
Open the Church Roles module and add all the church roles that you wish to share with your organisation. Note: Only create generic roles that you anticipate as being relevant to all churches in your organisation. For example, if each of your churches has pastors then add ‘pastor’ as a church role; if each church has an admin team, add ‘admin team’.
Once you have created all the roles you wish to share with the organisation, click the gear icon.
Tick the box Share these roles with the organisation.
If at a later stage you add a role to the Church Roles module, it will automatically be shared with all your churches.
If you delete a role it will be deleted from all your local churches.
Note: If a database is being used as the org level database and you have activated org level roles, then that database cannot have any custom roles. All roles in the org level database will be shared with the organisation.
Training your local church administrators.
If you plan on sharing org level roles across your organisation then it is crucial that you get your local church administrators up-to-speed. Org level roles will only be useful if all your churches populate them with the relevant info. There is little point to you setting up an org level role of 'Elder', but your local churches have their own custom church role of 'Elder', as they will then only end up populating their own list.
Your local administrators need to understand that the org level roles are designed to be the default roles for their congregation, and they should only create custom roles for positions in their church that are unique to their context.