FellowshipOne: Getting Started Guide

Here's what we suggest you do to get started with syncing GroupVitals and FellowshipOne (F1).

1. Before you ever sync, setup up a couple of test groups as you explore and learn how GroupVitals works (add/update groups & people, adjust account settings, take attendance, use the GroupFinder and/or general signup form, etc..) See our general  getting started guide here.

2. Review all of our  F1 documentation.

3. When you’re ready to sync, then we suggest you create a couple of test groups in F1 and assign them to a test F1 group type and sync that F1 group type with GroupVitals. Note that when you sync for the first time, it will sync over all the active people in your F1 database, but only the groups that are in your test F1 group type. Here's how to setup the sync.

4. When you're ready to sync over real F1 group types with GroupVitals, consider these two options. 1. Some churches sync just one F1 group type with GroupVitals, such as "GroupVitals Groups" which keeps things pretty simple. 2. Other churches will sync over lots of F1 group types. Typically, they'll create an F1 group type that matches each group type they've setup in GroupVitals. This way, when running reports in F1, you can view more specific information about people and the type of group they are in.

5. Spend some time seeing how the sync works (adding/updating groups, adding/updating people, taking attendance, etc..)

6. Add all of your leaders to their groups in GroupVitals, if they aren't in there yet. Once you add all of your leaders to their group, you're ready to send them an account invite email to create their account. Learn how to do that on step 3a. here. If you have more than 20 leaders, we can send out the invite to all of your leaders at once. Just send us a message and let us know when you'd like for us to send the email.

Let us know if you have any question by clicking the ? in the top-right navigation and selecting Contact Us 😊

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.