Mobile App Setup ================ Below you will find all the settings and features you will use to build and customize your app. Mobile Admin Settings --------------------- The Mobile App Settings are found in the database under `Admin > Communication > Mobile App > Settings` and are accessible to users with the AppAdmin role. Features > Feed .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2403071204.sfeed.png :target: # - **Enable Recommended People** - Make True to enable recommended people - **Enable Recommended Channels** - Make True to enable recommended channels - **Enable Recommended Prayers** - Make True to enable recommended prayers - **Enable Recommended Events** - Make True to enable recommended events Features > People .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061500.fp.png :target: # - **Enable Following** - Make True to enable following - **Follow Age Restriction** - Only users meeting the selected age restriction can be followed - **Status Flags for Who Can Be Followed** - People with these status flags can be followed - **Status Flags for Who Can Always Be Followed** - People with these status flags can always be followed - **Enable User Posts** - Allow users to create posts in mobile app - **User Age Restriction** - Limit posting to users meeting the selected age range - **Status Flag for Who Can Post** - People with these status flags can post in the mobile app - **Status Flag for Who Can Always Post** - People with these status flags can always post in the mobile app Features > Involvements .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2403071210.finvolve.png :target: # - **Enable Attendance for Leaders** - Make True to enable involvement leaders the ability to take attendance - **Number of Past Meetings to Display** - More information coming soon - **Number of Future Meetings to Display** - More information coming soon - **Past Meetings Max Age to Display** - More information coming soon Features > Chat .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061509.fc.png :target: # - **Enable Chat** - Please keep disabled until release - **Allow User Chat** - **Allow Involvement Chat** - **Conversation Limit** Features > Directories .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2403071222.sdir.png :target: # - **Include Archived People in Directory Search** - When true, archived people will be included in directory search results - **Include Business/Entity in Directory Search** - When true, Businesses/Entities will be included in directory search results - **Include Deceased People in Directory Search** - When true, deceaseed people will be included in directory search results Features > Profile .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061521.fpro.png :target: # - **Role for Enable Contact Download** - This is the role that is required to download contacts - **Alt Name Visible** - Make Alt Name visible - **Campus Visible** - Make Campus visible - **Role for Badges** - This is the role that is required to see badges in the mobile app - **Show Deceased Family Members** - When true, deceased family members will show in a persons profile Features > Events .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061525.fev.png :target: # - **Event Background Image** - Add branded background image for events page `NOTE:` Please try to keep file size under 1 MB - **Event Background Color** - Add color hex for background on events page - **Title** - Add your title for the events page - **Title Color** - Add color hex for events page title Features > Prayers .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2402051024.pry.png :target: # - **Prayer Background Image** - Add branded background image for prayers page `NOTE:` Please try to keep file size under 1 MB - **Prayer Background Color** - Add color hex for background on prayers page - **Title** - Add your title for the prayers page - **Title Color** - Add color hex for prayers page title - **Disable Prayer Feed** - Setting to True will hide the prayer feed from the menu and a person's profile. - **Require Approval for Feed** - When set to True, any prayer request submitted will require the "Include in Feed" keyword to be added for the request to show in the app feed. When set to False, all prayer requests submitted will automatically have the keyword "Include in Feed". To remove a prayer from the feed, remove the "Include in Feed" keyword. - **Number of Days to Include in Feed** - Prayer requests that were submitted prior to this many numbers of days will be included in the feed (if approved or auto-approved). - **Show Only First and Last Initial in Feed** - If set to True then only the first name and last initial will show for a person in the feed, and you can't click on a person's name to get to their profile. The prayer request will be associated to the person on the web side. - **Disable Anonymous** - Setting to True will prevent a user from submitting an anonymous prayer request through the app. - **Disclaimer Text** - When present, this text will display above the submit prayer request button in the mobile app. Features > Channels .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061531.ffc.png :target: # - **Leaders Visible** - Mark True to make leaders of channels visible - **Followers Visible** - Mark True to make followers of channels visible Features > Giving .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061534.fgi.png :target: # - **Background Image** - Add branded background image for giving page `NOTE:` Please try to keep file size under 1 MB - **Background Color** - Add color hex for background on giving page - **Title** - Add your title for the giving page - **Title Color** - Add color hex for giving page title - **Giving History URL** - Add giving history url - **Giving History Button Text** - Add your own giving history text for giving history button - **Enable One Time Giving** - Select True to enable one time giving option - **One Time Giving URL** - Add giving url for your giving page if giving is made outside of your TouchPoint database - **One Time Giving Button Text** - Add your own giving text for giving button - **Enable Pledge** - Select True to enable pledge giving option - **Pledge URL** - Add giving pledge url for your giving page if pledge giving is made outside of your TouchPoint database - **Pledge Button Text** - Add your own giving text for pledge giving button - **Enable Recurring Giving** - Select True to enable recurring giving option - **Recurring Giving URL** - Add recurring giving url for your giving page if recurring giving is made outside of your TouchPoint database - **Recurring Button Text** - Add your own recurring giving text for recurring giving button Features > Media .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061543.fm.png :target: # - **Background Image** - Add branded background image for media page `NOTE:` Please try to keep file size under 1 MB - **Background Color** - Add color hex for background on media page - **Title** - Add your title for the media page - **Title Color** - Add color hex for media page title - **Remove 'All' Filter** - When true, the 'All' filter will be removed from media categories Features > Campus Segmentation .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2403071234.scs.png :target: # - **Limit Channels to Campus** - Mark true to limit channels to campus - **Limit Events to Campus** - Mark true to limit events to campus - **Limit Prayer Requests to Campus** - Mark true to limit prayer requests to campus Features > Footer - This is a placeholder for when we add the ability to choose your own 5 footer options .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061601.fft.png :target: # Features > Feed .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061602.ffe.png :target: # - **Enable Recommended People** - Select True to enable recommended people - **Enable Channels** - Select True to enable channels - **Enable Prayers** - Select True to enable prayers - **Enable Events** - Select True to enable events Branding > Application Listing .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061611.bap.png :target: # - **Application Name** - Name your custom app, has a 30 character limit - **Application Description** - Add description of your app that will show in the app store - **Application Logo** - Upload application logo file which must be 1024 px by 1024 px with no transparency and no rounded corners - **Feature Graphic** - Your feature graphic must be a PNG or JPEG, up to 15 MB, and 1,024 px by 500 px Branding > Logos .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061613.bl.png :target: # - **Application Logo** - App logo on feed page - **Application Small Logo** - Small app logo - **Application Logo Light** - App logo used for dark background - **Application Small Logo Light** - Small app logo used for dark background Branding > Colors .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061616.bc.png :target: # - **Primary Color** - Add color hex for app primary color which needs to be a darker color than the secondary color - **Custom Color Palette** - This should only be used when you want to override the palette that is auto generated based on primary brand color - **Secondary Color** - Add color hex for app secondary color which needs to be a lighter color than the primary color Branding > Login .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061613.blo.png :target: # - **Login Background Color** - Add color hex for background on login page - **Login Background Image** - Add branded background image for login page `NOTE:` Please try to keep file size under 1 MB - **Welcome Title** - Add your title for the welcome page - **Welcome Title Color** - Add color hex for title color on the welcome page - **Welcome Mesaage** - Add welcome message to welcome page - **Welcome Video** - Add welcome video to welcome page - **Enable Username and Password Login** - placeholder for future option Branding > Default Background .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061619.bdb.png :target: # - `NOTE:` The default background picture will show up if there is not a background picture in place for the following pages: Media, Giving, Events, and Prayer. - **Background Image** - Add default branded background image `NOTE:` Please try to keep file size under 1 MB - **Background Color** - Add color hex for default background - **Title Color** - Add color hex for default title color Questions - Coming Soon .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061626.qu.png :target: # Recommended Image Sizes ----------------------- Below are the recommended image sizes for the app under Mobile App Settings: Branding > Application Listing **Application Logo** - This is the logo used in the app stores and what is displayed on your phone home screen. - The application logo must be 1024 x 1024 pixels with no transparency and no rounded corners. - `Note` - This will soon become two settings - one for iOS and one for Android since Android handles icons differently (based on device manufacturer). **Play Store Feature Graphic** - When you open the Google play store on an Android device this is the header graphic. - Must be a PNG or JPEG, up to 15 MB, and 1,024 x 500 pixels Branding > Logos **Application Logo** - Used in the following locations: #. Splash Screen Logo #. Feed header - Recommending size: #. We resize to a height of 200px #. No greater than 1 MB (can be smaller) **Application Small Logo** - Used in the following locations: #. Used in a loading screen #. Default hero image for channels if one does not exist #. iOS notification (this will be it's own setting soon) - Recommending size #. We resize to a height of 200px #. Ideally this would be a square badge image #. No greater than 1 MB (can be smaller) **Application Logo Light** - Used in the following locations: #. Background on the logo screen #. Typically a white or light version of the app so that it overlays on a background or dark image - Recommending size #. This should be the same size as the Application Logo #. We resize to a height of 200px #. No greater than 1 MB (can be smaller) **Application Small Logo Light** - Used in the following locations: #. Recommended widgets #. Used on events card if no background image #. Android notification (this will be it's own setting soon) - Recommending size #. This should be the same size as the Application Logo #. We resize to a height of 200px #. Ideally this would be a square badge image #. No greater than 1 MB (can be smaller) Branding > Login **Login Background Image** - Recommending size #. This sizes to the width of the device and fades into the background color #. No greater than 1 MB (can be smaller) Branding > Default Background **Background Image** - Recommending size #. This sizes to the width of the device and fades into the background color #. No greater than 1 MB (can be smaller) Features > Events **Event Background Image** - Recommending size #. This sizes to the width of the device and fades into the background color #. No greater than 1 MB (can be smaller) Features > Prayers **Prayer Background Image** - Recommending size #. This sizes to the width of the device and fades into the background color #. No greater than 1 MB (can be smaller) Features > Giving **Giving Background Image** - Recommending size #. This sizes to the width of the device and fades into the background color #. No greater than 1 MB (can be smaller) Features > Media **Media Background Image** - Recommending size #. This sizes to the width of the device and fades into the background color #. No greater than 1 MB (can be smaller) **Other notable recommended images sizes in the app:** Registration/Channel Image **Location: Under Registration > Mobile Sites > Photo** - Recommending size #. This sizes to the width of the device and fades into the background color #. 600 px (wide) x 240 px (high) #. No greater than 1 MB (can be smaller) Channel Badge **Location: Under Registration > Mobile Sites > Badge** - Used as the hero image for channel posts - Recommending size #. Ideally this would be square #. 100 px x 100 px #. No greater than 1 MB (can be smaller) Banner Image **Location: Under Admin > Communication > Mobile App > Banners** - Recommending size #. 320 px x 180 px #. No greater than 1 MB (can be smaller) Media & Resources ----------------- Setting up Media & Resources Media & Resources are added to the database and then are populated in the app for specific users determined by the creator of those resources. For more information on this process refer to the `Media & Resources article `_. Specifics on how media & resources work within the mobile app Media & Resources are found in the app in these two locations: #. The hamburger menu in the upper right corner #. The footer of the app on the Media icon **How is content organized?** - In the above article you'll see how to organize content into Tabs and Groups, this translates into sections and groups in the mobile app. **What types of media are supported?** - **Livestream** - Livestream resources can be set as either one time or recurring and will show only during a specified window. You simply enter the livestream link and details and we take it from there. Available live streams will show at the top under Live. .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310041416.tlive.png :target: # - **Audio** - Enter a URL to a hosted audio file (I.e. mp3) or optionally you can add a speaker and date. - **Video** - Enter a URL to a hosted video file (mp4 or m3u8), Vimeo or YouTube Link or optionally you can add a speaker, date and link to the giving page of your choice. .. note:: For Vimeo and YouTube videos, the URL required must be a direct link to the video itself and the URL should not include additional information as if it were from a playlist or some grouping. `Correct Example Link` https://vimeo.com/(videoID) and this is the same for YouTube videos. - **Weblinks** - Include any weblinks. - **PDF** - Upload one or more PDF documents. - **Freeform** - This resource can be used to embed any HTML content of your choosing. **Note:** Make sure your content is mobile responsive so that it displays properly in the app. **Who has access to what resources?** - **Options include** - Visible To Everyone (default) or a combination of the following pictured below: .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310061636.mnr.png :target: # Events ------ Overview The mobile app has 2 ways to set up registrations, depending on the needs of the event, that enable a quick and easy registration process for users. Since the user is known by the app, it still remembers the login and process and saves several steps for the person registering. Registration Types For registrations requiring payment and/or additional questions besides just knowing who is planning to attend you have two options: #. **Regular Registration** - This links out to a registration form where the user is already logged in and can simply enter the final details necessary, make a payment (if needed) and register. #. **RSVP Registration** - This simply allows the user to RSVP with a simple click of a button. No additional information is gathered besides who is registering. Settings specific to Involvement Registrations .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310041509.eopt.png :target: # | - **Show In Mobile** - Show registration in app by checking this box - **Show in Sites** - Show registration in TouchPoint Sites, only if you have sites enabled on the database - **Registration Type** - This allows you to set which type from the list above. - **Registration Button** - You can customize the registration button text to your liking, the default text is Register - **Category** - Events can be organized by category for ease of finding/sorting. An admin user can customize these categories and set the sort order in the lookup codes. - **Campus** - This determines which users see which events. Users will only see events that match the campus on their record and events that are set to not specified. - **Start Date** - This determines when the event will be listed in the mobile app. - **End Date** - This determines when the date after which the event will no longer show in the mobile app. - **Show Registrant Count** - This determines whether the list of registrants will be visible to other users who might also be interested in registering. - **Enable Channel** - Enable the involvement as a channel in the app. - **Photo** - Here you can set the photo that shows in the app for the event. - **Badge Photo** - Upload the badge photo as you want it to appear on your custom mobile app. To see this badge photo on the Involvement Search Mobile View, set Include in Mobile App=True. - **Description** - This setting allows you to add a description and include any other necessary event details. Managing/Viewing all Events/Registrations in One Place There will be a new tab on the Involvement Search Page that will allow a user to view and manage all registrations in one place but for now please use the Mobile 2.0 View tab. (stay tuned) In App Giving Page ------------------ A partner church must be approved through Benevity or Candid to accept donations within a mobile application. Without this approval, giving pages must be opened outside of the application. To allow the application to open giving pages within the app, you can register and create an account at `benevity.com `_ or through `candid.org `_ After you have registered, in your TouchPoint database you will need to add your Charity Verification information. This is found under `Admin > Communication > Mobile App > Settings > Branding > Application Listing > Charity Verification.` The following Settings will need to be completed: - **Charity Verification Provider** - Select your Charity Verification Provider, Benevity or Candid. If None is selected, giving links will open in a mobile browser outside of the application. - **Charity Verification Profile** - Supply a link to your Charity Verification Profile. This may be required when publishing your application to the app store and is found on your Benevity or Candid profile page URL. .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2401051015.cv.png :target: # Giving Impact Cards ------------------- Overview Giving Impact Cards are the first thing a user sees when a person clicks on the giving link in the footer and are intended to inspire people to deeper levels of generosity. Cards can be completely customized by each church, and you set which people see which cards based on what you know about them. Examples to how you might set up Impact Cards - **Missions** - If a person has been on a mission trip, expressed interest in missions, or made a gift to missions in the past you might consider showing them a Missions impact card that visualizes the impact of your mission's programs (i.e. stories of changed lives, impressive stats, etc.). - **Children's Ministry** - If a person has children or serves in the children's ministry you might consider showing them a Children's Ministry impact card that visualizes the impact of the children's ministry. - **Other example of Impact cards to consider:** #. Year-to-date giving updates #. End of year giving appeal #. Special giving Initiatives - Campaigns, disaster relief, etc #. Ministry Specific Updates #. Top Donor Impact #. How a first-time gift makes a difference - **This feature is only limited by your imagination.** .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2303300913.IMG_0026.png :target: # Where and how to set up impact cards? - Impact cards are managed under `Admin > Advanced > Special Content > then select in Keyword Filter Mobile Giving` where there are 3 example cards you can use as a template to create your own cards and can be set up by anyone with the Admin and/or one of the Special Content roles. - This will display two new settings: #. **Mobile Rank** - If a person has more than one impact card to display on their giving page this determines the order of the cards. #. **Status Flag** - People that meet the criteria for this flag will see the specified card. **Note:** Make sure you leave the status flag blank on at least one card so that each person using the app will have a default card. .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2302131219.scmob.png :target: # - Any new HTML file you create needs to have the keyword set to Mobile Giving - Customize the card using HTML and add photos, text, and graphics to make it appealing and interesting. Make sure you test the card to ensure the content is mobile responsive and easy to view on the mobile device. Mobile Tip Cards ------------------- Overview Mobile Tip Cards are the first thing a user sees when a person has logged into the app and is intended to give tips on navigating the app. Cards can be completely customized by each church and there are some templates in place you can choose to use or create your own. Examples to how you might set up Mobile Tip Cards - **Profile** - Use this card to explain how a user can get to their profile and keep their information up to date - **Giving Page** - Direct users to the giving page - **Events** - Direct users to the registration events page - **Directories** Explain how directories work and how a user can access their directories - **This feature is only limited by your imagination.** .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310130943.mt.png :target: # Where and how to set up Mobile Tip cards? - Mobile Tip cards are managed under `Admin > Advanced > Special Content > then select in Keyword Filter Mobile Tip` where there are 6 example cards you can use as a template to create your own cards and can be set up by anyone with the Admin and/or one of the Special Content roles. - This will display the 6 example cards and can choose to create them how you like .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310130957.scmt.png :target: # - Any new HTML file you create needs to have the keyword set to Mobile Tip - Customize the card using HTML and add photos, text, and graphics to make it appealing and interesting. Make sure you test the card to ensure the content is mobile responsive and easy to view on the mobile device. Messages & Push Notifications ----------------------------- Messages & Push Notifications - Messages can be pushed to a person in the mobile app using the Blue Toolbar envelope icon under `Mobile > App Message/Notification`. Add a Start Date/Time for when you want the message to send. An Expiration Date/Time can also be used to determine when you would like the message to be removed from the feed. .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310101427.sm.png :target: # - Messages can be created and sent if a few different ways: #. **Standard Message** - Send a standard message #. **Alert Message** - Send a alert message that will show in yellow at the top of the user's feed #. **Include Push Notification** - You can also send a Push Notification with the Message if needed, not all messages would require a push notification. If a user has notifications enabled for your church's app and General notifications set to on in their settings, then they will get a push notification. How are messages sent? - Messages are either sent from the Blue Toolbar or automated through the process builder - When sending from the Blue Toolbar you'll see who (from your selected list of recipients) has either: #. **Logged into the mobile app** - These individuals will get the message #. **Logged in and has push notifications enabled** - These individuals will get the message and a push notification #. **Not a mobile user** - These individuals will not get a message or push notification - From here you can add a title, message and select from one of the calls to action (coming soon). Who can send messages? - Currently, any user with the AppAdmin role is able to send messages from the Blue Toolbar. Messages Log - All sent/schdeuled messages can be tracked under `Admin > Communication > Mobile App > Messages Log` History on a person's communications tab - Under the Communications and Messages tab, you will be able to see the messages for that individual. Directories ------------------- Customizable Directory Overview - Sadly, we are past the days when we used to be able to print a directory with all attendee's contact information for everyone to see. Data sharing and privacy concerns make sharing contact information a real challenge. - The good news is that the way we've set up Directories/People Search in the mobile app allows you to set very granular permissions based on relationships that exist within the church. A congregant can then manage their specific privacy preference and override (share more or less) based on their comfort levels. Examples You can now uses directories based on how people are involved and make decisions about what should be shared based on how intimate the group is. - **All Regular Attendees** - This is likely your largest group and might allow people in this group to see other people's names and photos only. - **Members** - This is a more committed group and could allow additional information to be shared like basic contact information. - **Sunday School Class** - These people are more likely to know everyone in the group and you might allow more information to be visible like family member names. - **Small Group** - This is likely your most intimate and connected group and it might be appropriate to let fellow members see all the available fields about each other. - **NOTE:** You can set as many or as few groups as you'd like. If someone is in more than one group with another person, the group that allows more data to be visible will define what is visible between the two individuals. How to set up .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2302131506.direct.png :target: # - Directories are enabled on a per involvement basis using the setting seen above. - **Available Fields** - each directory can set which fields are visible by default (a user can override) #. Age #. Day/Month #. Year #. Address #. Email #. Phone (cell) #. Family Members #. Related Families - Any individual who is a member or leader of an Involvement directory will have access and what information is shown about them can be customized. `Please see our documentation about using and setting up this feature. `_ - Report to see which involvements have directories enabled coming soon Managing Privacy settings for a person - A person can set specific privacy settings per involvement or set a default that applies to any directories they are on. - **In Mobile** Under the Directory Search and after selecting a directory, click the three vertical dots in the upper right corner to choose the global settings for all directories or the directory settings for that specific directory. Toggling these options lets the user override the default settings set by the leader of the directories. .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2302131531.psetapp.png :target: # - **On Web** #. Per Involvement Settings are managed in the system dialogue box for each involvement previoiusly mentioned in the "How to Setup" section #. The default can be controlled on the person's profile under the tab `Personal > Privacy Settings` .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2302131627.mainpsett.png :target: # Directories Report Under `Admin > Communication > Mobile App > Directories Report` you can view a list of the current enabled directories and and details about them. - Clickable Involvement ID link - Name of Directory - Involvement Type of Directory - Campus - What information is available to view about the members in the directory - Number of people in the directory .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310031156.direp.png :target: # Chat (Coming Soon...) --------------------- Channels -------- Overview Channels allow a mobile app user to customize the content that shows up in their feed based on what they follow. This creates a dynamic and personalized feed on what the user is interested in versus the traditional method of sharing all communications with everyone. This tool can be paired with the process builder (read more below) to “pre-build” interests for a user based on their involvements or what you know about them. .. note:: It is recommended that a **Channel is created as a stand alone involvement** and not to be used with an involvement that is a registration. There is a risk in doing this because if someone unfollows the channel it will make them a previous member of the involvement, basically unregistering them for the event. Examples Your church can completely configure this feature and set which channels are available to users. Here are some examples of channels you might want to setup. - General Church Updates - Campus or Location Specific Ministries - Children's Ministry #. Nursery #. Pre-school #. Elementary - Youth Group - One for Parents, One for Adults - Demographic or Interest Based #. Men's Ministry #. Women's Ministry #. Singles Ministry #. College & Early Career #. Senior's Ministry #. Faith & Work #. Sports Ministries - Leadership Channels - Discipleship - Scripture - Demographic or Interest Based #. Small Group Leaders #. Elders #. Deacons - When first setting this feature up we recommend that you begin on the smaller side and only create channels that have active leaders who will post interesting and relevant content that will engage the intended audience and keep them coming back for more. You are only limited by imagination as to what you want to set up. Pair with Process Builder Set up a saved search and use the process builder to automatically add anyone that meets the set criteria to the involvement. - An example would be to add all men over the age of 21 automatically to the Men's Ministry involvement - If there isn't a clear search condition that matches a particular ministry consider automatically adding anyone that has participated in that ministry on an ongoing basis. - Automating who initially follows a channel can ensure that when someone logs into the app for the first time they have relevant content immediately. It can also prevent people from falling through the cracks that aren't as good at managing their interest or preferences. - **NOTE:** If you plan to use the above recommendation to automatically add people to involvements based on what you know about them or their activity, it is important that you build into the search to not add people that are already previous members of the involvement. This will prevent you from re-adding someone that decides to unfollow a ministry at some point in the future. Configuration We recommend creating either a new Program/Division and/or Involvement Type to organize all the “Channel” involvements before you start creating them. This will help you stay organized and see all available options in quick view. **Settings:** - **Per Involvement** #. **Enable Channel** - Under `Registration > Mobile/Sites` turns on the involvement as a “Channel” #. **Allow Following** - This is checked by default when a involvement is enabled as a “Channel” and allows you to turn off an involvement from showing in the feed as “recommended” and a user from following it on their own. This is a great option for a ministry like “Small Group Leaders” or “Members” that have additional requirements to join and where you want to populate who can follow or not. #. **Photo** - Upload a photo here to personalize and brand the channel #. **Badge Photo** - You can include a badge photo which will show as a hero image in the app attached to that involvement. - **Mobile Admin Settings** #. **Leaders visible** - This determines whether the leader's photos and names are displayed on the channel's page in the mobile app #. **Follows visible** - This determines whether the followers of a channel's photos and names are displayed on the channel's page in the mobile app **How campus impacts “Channels”** - A user will only see “Channels” that match the campus of the signed in user and those that don't have a campus. If you'd like a channel to show up across multiple campuses then leave the campus setting as not specified. **Who can post on behalf of a channel?** - Anyone you set as a leader member type in the Involvement will be able to post on behalf of the channel in the app. You can set as many or as few leaders as you'd like. Based on the setting above, remember that leaders of the channel might be visible to anyone who follows the channel. **How?** - After navigating to the channel's name, a leader can click on the three dots in the upper righthand corner to “Post” Channels Report Under `Admin > Communication > Mobile App > Channels Report` you can view a list of the current enabled channels and the details about them. .. figure:: https://c4265878.ssl.cf2.rackcdn.com/trialdb.2310031655.chrep.png :target: # | | +--------------------+------------------+ | **Latest Update** | **1/15/2024** | +--------------------+------------------+ Added recommended image sizes