Core Team App Setup

This gives staff and the Core Team a practical overview of the app's messaging, access, and safety tools.

Main Idea

The app replaces church center but also does things a little bit different than church center, a lot of features will be discussed so instead I'm having AI write a bunch of useful steps and slop for you to read that way I don't have to. There will be a lot of information, this one section will have all of the cruticial info.

Detailed Info:

• Core Team Setup
• Group Chat and City Groups
• Channels and Announcements
• Messaging Safety and Moderation

Choosing the Right Kind of Conversation

Direct Messages

A direct message is a private conversation between two people. Everyone can start direct messages without receiving a special church permission.

Regular Group Chats

A regular group chat is for a defined team or short list of people. It works well for day-of teams.

Regular group chats are limited to 32 total members, including the person who creates the chat.

Only people with the Create group chats church permission can start a regular group chat.

1. Open Messages.
2. Tap New Conversation.
3. Choose New Group Chat.
4. Add a name and optional photo.
5. Select at least one person.
6. Tap Create.

The chat owner or an admin can add and remove members later, up to the 32-member limit.

City Group Chats

City Group chats are the important exception to the regular group-chat limit and membership process. A City Group chat can only be created by someone who is a leader of that City Group and has their GCT account linked to their Planning Center (PCO) profile. Once both requirements are met, the leader creates the chat from the group's Manage tab by choosing Create Group Chat.

Membership is then managed by the City Group itself:

• When someone with a GCT account joins the City Group, they automatically join its chat.
• When someone leaves the City Group, they automatically leave its chat.
• Leaders cannot manually add or remove people from the chat alone, they have to be removed from the city group.
• The regular 32-member group-chat limit does not apply.

Active PCO leaders are automatically made admins in the City Group chat, while regular City Group members remain normal chat members.

City Group leaders can also turn on Announcement Mode when only leaders should post. The conversation owner and admins can send messages and react. Normal active members can still read and react, but their message composer is disabled.

Channels

Channels are for broader communication and are not limited to 32 members. Only people with the Manage channels church permission can create them.

When creating a channel, leaders can choose whether it is public:

• Public Channel on: Anyone in the church can discover and join it.
• Public Channel off: Only invited members can access it.

A channel can also be changed into an Announcement Channel from its conversation settings. The conversation owner and admins can send messages and react. Normal active members can still read and react, but their message composer is disabled.

Someone viewing a public channel has to join it before they can react.

Public and announcement are separate settings. A channel can be public, an announcement channel, both, or neither.

How Staff Give Access

Church permissions are granted from a person's profile. Only authorized staff with church permission-management access will see these controls.

1. Open People.
2. Search for and open the person's profile.
3. Tap Add Church Permission.
4. Select the narrowest permission that matches the person's responsibility.
5. Confirm the grant.

The main messaging permissions are:

To remove access, return to the person's Church permissions, swipe left on the permission, tap Revoke, and confirm.

Manage Announcement Settings

The owner or an admin of a channel can control who is allowed to post:

1. Open the channel.
2. Tap the channel name or header to open its settings.
3. On the Info tab, turn Announcement Channel on or off.

For a City Group chat, the same setting is called Announcement Mode.

Use announcement mode when the purpose is clarity and distribution. Leave it off when the purpose is participation and discussion.

Control Reaction Alerts

Every member can adjust reaction notifications for each conversation. Open the conversation settings and choose a Reaction Alerts option:

• On: Receive reaction alerts for the conversation.
• My Messages: Receive alerts only when someone reacts to a message you sent.
• Off: Do not receive reaction alerts from that conversation.

Members can also choose Mute Alerts to mute the entire conversation for a selected amount of time.

All mute settings only apply to the yourself.

Reporting, Blocking, and Moderation

These tools solve different problems. Reporting flags content for review, blocking protects a member's personal space, and moderation is a staff action that changes another person's access.

Report a Message

Anyone can report a message they did not send:

1. Press and hold the message.
2. Tap Report.
3. Choose Inappropriate Content, Spam, or Harassment or Bullying.
4. Confirm the report.

The app submits the report and immediately hides the reported message behind a placeholder for the person who reported it.

Whenever a staff member gets their message reported, it instantly sends it our senior pastors Andrew and Christina Gard. (kidding)

Block a User

Anyone can block another user from that person's profile:

1. Open the person's profile.
2. Tap Block User.
3. Confirm the action.

A blocked user cannot message the person who blocked them. Blocking is personal and does not ban the blocked user from the church app. A member can review and undo blocks from Settings > Blocked Users.

Staff Moderation

Authorized staff with the Member moderation permission will see a Moderation section on another member's profile.

• Restrict Messaging: Bro will now be muted for life. The member can still enter the app, and read messages, but cannot send messages anywhere in it.
• Ban from App: The member loses access to the GCT app and is signed out when the app next checks their access. The ban also blocks public GCT data from being viewed, and this is a device ban, so the user will not be able to log back into their account or any other account.

Both actions allow an optional internal reason and stay in effect until an authorized leader lifts them. Use the reason field to leave a brief, factual record for other leaders.

TLDR