Campus¶
If your church has more than one campus or site, your TouchPoint Administrator can create those Campuses in your database. You will then be able to assign the appropriate Campus to Involvements and people.
- Campus¶
TouchPoint uses Campus designations for both Involvements and People records for churches that meet the following criteria:
The church has multiple locations.
They consider themselves to be one church, even though they have more than one site.
They want their data in the same database.
A Campus designation is used in several places. The most important use of Campus is for check-in. If you use TouchPoint Check-In and have multiple Campuses, you will probably want to display only the classes meeting at the specific campus / location where the person is checking in. In other words, if a person visits the East Campus, you do not want to display classes for check-in that meet at the North Campus. For that reason (and others), you will want to assign a Campus to your Involvements.
A Campus is also assigned to people records. The Campus is assigned automatically to new records based on the context in which the new record is added. See below for more about that and how Involvements have their Campus set automatically as well.
Campus displays on many of our Excel exports. It can also be used as a filter on Contribution reports and Membership / Decision reports. You can also use Search Builder to find people based on their Campus. You may even want to create Bundle Types that correspond to a specific Campus.
Another word about Campuses and Check-In
Please read about the settings that relate to check-in, especially the setting Allow Non-Campus Checkin and how that works. This will help you understand how to set the startup settings for Check-In and how to flag individual Involvements.
See also
Create Campuses¶
A user with the Admin role creates the Campuses in the Lookup Codes table.
- Step 1
Go to Admin > Advanced > Lookup Codes, and then select Campus under the Involvements heading.
- Step 2
Click the green Add Campus button, enter the New ID number and click Submit. This creates the new Campus ID, and the new row is highlighted for a few seconds.
Caution
Be sure to enter an integer, not the Description.
- Step 3
Next, you need to edit the Code and the Description. Click in the text field where it says Empty.
The first field to edit is the 2-character Code. It can be any 2 letters that are not already in use.
The next field to edit is the Description which will display in drop downs and on Involvements and people records.
Tip
You can use the directions below to assign a Campus to individual Involvements. Or a user with the Admin role can use Admin > Involvements > Update Involvements to update multiple Involvements at once.
See also
Campus Name Change
To rename a Campus after it has been created, update its Lookup Code.
Go to Admin > Advanced > Lookup Codes, and then select Campus under the Involvements heading.
Click in the Description, change the text, and click the blue check mark.
Follow the same process to change the Code for that Campus.
This will change the name and code everywhere it is used in your database.
Assign a Campus to an Involvement¶
Once you have multiple campuses, you need to assign each Involvement to the correct campus. Any user with the Edit role can do this.
- Step 1
Go to the Involvement and click Edit on the Involvement header.
- Step 2
Select the correct Campus from the drop-down and then click Save Changes.
Assign a Campus to an Individual¶
See below for how this is automatically set for new records. Any user with the Edit role can set the Campus for existing records (see EnforceEditCampusRole below for an exception).
- Step 1
Go to the person’s record and click the pencil icon in the Campus badge. If no Campus is set, you will see No Campus displayed.
- Step 2
Select the correct Campus from the drop-down and click Save.
Note
A user with the Admin role can change the Campus for a Tag of individuals by using Admin > Tools > Update > People.
Setting a Campus Automatically¶
Campus is set automatically for both new Involvements and new people records after you have created your multiple Campuses and have assigned them to existing Involvements, and to existing people records.
This is how that happens:
- Guest or New Member to an Involvement
When a person is added to the database because they visit or join an Involvement, they will be assigned the Campus that is associated with that Involvement.
- New Family Member
When a person is added directly to a family, they will be assigned the Campus of the Head of Household.
See also
- Add New Person
When a record is added to the database without any context, the record is assigned the Campus in the DefaultCampusId Setting (see below). In other words, this is when the person is added by using People > Add Person in the main menu. If DefaultCampusId is not set, the Campus is blank unless one is selected on the Add Person form.
- New Involvements
When you add a new Involvement, it will have the same Campus as the Involvement you are viewing when you click Add Involvement.
See also
Settings Relating to Campus¶
TouchPoint has several optional Settings relating to Campus.
- CampusIds
If you are using ShowCampusOnRegistration, you must also add this Setting to indicate which Campuses you want to offer as options for a new record. This applies only to the drop down that displays when a registrant creates a new record during an online registration. Enter the Campus ID numbers separated by commas without any spaces. You can enter all the Campuses or only a select few.
- CampusRequired
If you add this Setting with the value true, every new record requires that a Campus be selected. The option to leave the Campus blank is removed from the Campus drop-down.
However, if you do not want registrants to be required to select a Campus when they register online but want it required everywhere else, check Not Req Campus on the Involvement’s Registration > Registration tab. The Campus drop-down still displays for the registrant, but a selection is optional.
See also
Registration Settings Tab - see Campus Requirement section.
- DefaultCampusId
Add this Setting with the Campus ID of the Campus to assign to new people records that are added without context (such as People > Add Person). You can change the Campus on the record afterward if needed.
- EnforceEditCampusRole
Add this Setting with the value true when you want only users with the EditCampus role to be able to change the Campus on a person’s record. This applies only to the Campus field on a person’s record, not to setting the Campus for an Involvement. After adding this Setting, add the EditCampus role in the Lookup Codes and assign that role to everyone who should be able to edit the Campus for an individual.
Exceptions: Users with the Edit role can still change the Campus for their own family when they are the head of household or spouse. Users who can edit their own family’s address can edit their family’s Campus when MyDataCanEditCampus is also true.
- MyDataCanEditCampus
To let My Data users edit the Campus on their own people records and those of their family members, add this Setting with the value true.
- ShowCampusOnRegistration
With this Setting added and the value set to true, all new records that are added during an online registration will be presented with a drop down to select a Campus. The registrant is required to make a selection unless you check Not Req Campus on the Involvement’s Registration > Registration tab.
See also
Registration Settings Tab - see Campus Requirement section.
- SortCampusByCode
To change the default sort order of the Campus list, add this Setting and set the value to true. Then set the order in the Lookup Codes. Click in the Code field for each Campus and enter the sort as a number followed by a dash in front of the existing Campus Code. Example: 1-AP, 2-AR, 3-BV, and so on.
See also
The help article below explains how to add these Settings and has descriptions of all possible Settings.
See also
Latest Update |
10/22/2026 |
Corrected the Lookup Codes path, the default Campus for new records, the CampusRequired and EnforceEditCampusRole behavior, and added role requirements.