Special Content

Users with the Admin, SpecialContentBasic, or SpecialContentFull roles can access this at Administration > Setup > Special Content. This is where you (the TouchPoint System Administrator for your church) will find some public facing pages, scripts, and more. You can edit these using an intuitive WYSIWYG editor.

There are several tabs in Special Content:


The SpecialContentBasic role allows a user to access just the first 2 tabs (HTML Content and Text Content). The SpecialContentFull role allows a user to access all 4 tabs.

HTML Content

This contains emails and other public-facing pages that you can edit. This is also where you can create Shells for online registrations.

Edit an existing file:
Click the Name of the file, make your changes and then click the Save Content button which is below the text editor.

You can edit this to say what you want. You might want to include a RegisterLink so a registrant can return to manage his subscriptions at any time. This is the used with the online registration type Manage Subscriptions.

Create a new file:
Click + New HTML File to add a new file, if your database does not have one that is listed below. Be sure to enter the Name exactly as it appears below.
Create a new Shell
If you are adding a new Shell, the Name should contain no spaces (although the title can contain spaces). For online registrations, enter the Name of the Shell (not the Title) on the Registration > Registration tab in the Advanced Settings section.


For each of the items below that are email notices, the Title will be the subject of the email. The Name must be entered as you see it below.

This notice is sent when a registrant selects Save Progress in the course of an online registration. The message contains a link to allow them to return and complete their registration using the special Email Replacement Code [registration for {orgname}]. This inserts the name of the organization or the registration title, if there is one. Example: registration for Mission Trip to Uganda 2015
This is the notice that is sent when a person, who is already in your database, registers online and uses an email address that is different from the one on their people record.
This is the email a person will receive if they check the Create Account box during the course of an online registration, and they already have a user account.
This notification is sent to your System Administrator when someone clicks Forgot Password on the login page and enters a bad email address.
This email is sent when someone clicks Forgot? on the login page, if they enter a good email address and that email is on the person’s record in the database.
This is what displays as the header for your church’s TouchPoint database - that is, the name of your church and a byline.
This is the email sent when someone is given a user account and the Send Welcome box is checked. It is also sent when a person clicks Need an Account? Request a password link from the login page.
This message is sent to someone who registers online for an event, but does not have an email address on their people record.


The OneTime notices listed below are used when a person is not logged in and is using one of these types of registrations:

  • Manage Recurring Giving
  • Make a Pledge
  • Manage Subscriptions
  • Manage Volunteer Slots

For these, we always send a one-use link for security reasons. So, your email must include a link. Example: Click HERE to manage your recurring giving.

Highlight the text you want them to click, select the link icon from the toolbar, and enter the text {url} and click OK.

You can also use either {name} or {first} email replacement codes in these.

The Title of the file (not the Name) will be the Subject of the email. You must use the exact Name as indicated below.

This message is used for Manage Subscription registration types.
This email is sent to someone making an online Pledge.
This email is sent when volunteers need to manage their time slots.
This email allows a person to set up their recurring giving.

Most database will already have these One Time Confirmations in Special Content > HTML Content. If they are missing in your database, the first time someone triggers one of these, the default message will be displayed in HTML Content. At that point, you can edit it if you choose. Or, if you prefer, you can create the HTML file using the exact names listed above and entering the link as described.


The RecurringGifts notices are sent to notify donors that their recurring gift has either been processed or that it failed.

For these 2 notices, in addition to those indicated below, you can use other standard email replacement codes, such as {first}, {last}, {address}, {csz}, and so forth.


This email is sent to a donor when a recurring gift is processed. This happens at 4:30 AM (Central) time.

You can use the email replacement code {total} to indicate the total amount of the donation or you can create a notice that uses the same format as the Recurring Giving Management Confirmation, which will indicate the breakdown by fund.


This email is sent when a recurring gift fails to process when the batch is run.

Use the email replacement code {message} to display the message from the payment processor. This will be the reason the payment failed. You can also use {total} to display the amount of the donation.

This file contains the default message the user will see after he enters his username or email address when he clicks the Forgot Password? link. You can edit that message if you want to add the phone number for the church or more information. The very first time anyone clicks the link to request a new password for your database, this file will get created. So, it will probably be in every database except brand new ones. If you do not see this file in your database, log out and click the Forgot Password? link yourself and then check the HTML Content file.

This is the email that a person receives when they click on a SendLink or SendLink2 in an email. Each database will have a default email, but your System Admin can edit it.


This is the header on the Contribution Statement. Each church will need to customize this for their church.


This is a section on the Contribution Statement where you can put a ‘no goods or services…’ message.


The following three items relate to the Volunteer Calendar. The first time one of these emails is sent (normally that would be when you are testing the org), the HTML will become available for editing in Special Content. Notice the email replacement codes.


This is the email a leader will send when requesting a additional volunteers.


This email is sent to a volunteer that agrees to substitute for another volunteer.


This is the email a volunteer will send to request a substitute.


Text Content

This is where special scripts are stored.


This is an IronPython script for the automation of the membership process. This also includes the automated process for changing Marital Status, dropping all Enrollments, etc. when you mark a person as deceased.

There is a Setting UseMemberProfileAutomation that each church can set to either true or false, depending on whether the want to use this or not.


If your church wants to continue using the Deceased process, but not the other membership automation processes, see the article below.


If you would like to combine specific Giving Funds for reporting, you can create this Text File where you can specify which funds should report together. You can also specify a set the contains only one fund.

One use case would be to combine all the funds for each specific Campus, or you could combine your Budget Fund with a special Pledge Fund. You can also create a set for just your Budget Fund.

See also

Custom Fund Sets


Each database has a set of 3 custom reports that users can access from the toolbar under the cloud icon. They are Email, Student and Parents, and AllColumns. The scripts for these are in this section of Special Content.

To create any new custom reports, you will use the New Custom Report option on the blue Toolbar. This is under the code icon. When you save the report it will automatically get added to this file.

See also

Custom Reports

This file will list all of the custom reports including SQL and Python reports. The most recent report created will appear at the bottom of the list. You will probably want to edit this in order to keep the reports in some sort of order.

This is a script that defines which Standard Extra Values you want to appear on every person’s record.


This is the script for the Vital Stats report which is found under the Reports menu in the Header.

See also

Vital Stats

Sql Scripts

These are special scripts that are either already in your database or that you can easily add to your database by copying and pasting the SQL recipes that we have in the documentation. These are used to add special reports. Some run from the Blue Toolbar People, Blue Toolbar OrgSearch, or the Main Menu. You choose whether to add the scripts to the toolbar or not.

Python Scripts

These are special Python scripts are used to run various processes. Like the SQL scripts, you can add these to your database by following the recipes in our documentation.

Latest Update 5/12/2021

Added info about SpecialContentBasic and SpecialContentFull roles