The Contact Management System (CMS) is an online system that holds contact information for people who hold selected parish, deanery and diocesan posts.
Each postal address, phone number or email address has its own privacy setting. There are three options:
- PUBLIC means that consent is given for it to be included in diocesan publications (e.g. the Diocesan Yearbook) or shared with anyone who asks for it.
- DIOCESE means that it will only be shared with people in the diocese who have an authorised role (clergy, readers, churchwardens, PCC officers, diocesan staff, etc.).
- PRIVATE means that it will only be shared with diocesan staff and a few other authorised users.
For parish clergy, 'Public' also means that consent is given for it to be displayed on the diocesan website.
By default, the initial privacy setting for contact information is 'Diocese' (as indicated on the CMS by a yellow padlock). However, a contact can easily change their privacy settings to 'Public' (green padlock) or 'Private' (red padlock).
Conditions of Use
By applying to use the CMS, users agree to the following conditions of use:
- Contact information must only be used for the purpose of furthering the mission and ministry of the Church of England.
- Contact information will only be shared in accordance with the individual's privacy settings.
- The CMS will not be used to send unsolicited emails or letters to groups of people.
- The CMS will not be used to compile group email lists (but see below).
These conditions are in accordance with the diocesan data protection policy. Any breach of these conditions may result in access to the CMS being withdrawn from a user.
Advance Features for Deaneries
The CMS has several advanced features that can be enabled for Area Deans and deanery officers. These include:
- Sending emails to specific groups within the deanery (eg Deanery Synod members);
- Printing address labels for specific groups.
These advanced features need to be enabled on an individual basis. Please send any requests to firstname.lastname@example.org