> For the complete documentation index, see [llms.txt](https://docs.joingather.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.joingather.org/admin-hub-guide.md). # Admin Hub Guide Welcome to your comprehensive **guide to the Gather App Platform Admin Hub**. We’ve sprinkled in short, 3-5 minute tutorial videos at the start of each section below to walk you through core capabilities, followed by a written walk-through with images Tap the **Ask** button in the top left corner to use AI to help find quick answers Please let Gather Support know if you have any questions. ## Gather App Introduction Home + Events {% embed url="" %} ## Web Hub Introduction {% embed url="" %} Hello! Welcome to the Administrator Hub for your Gather app. We’re here to walk you through all the essentials: creating events, adding resources, adding members and more! ## Events ### Basic event management {% embed url="" %} Event creation is as easy as 1, 2, 3! 1. Navigate to the **Events tab** using the sidebar or the button on the home page. 2. Select the community (or one of the communities) you wish for the event to be in 3. Press the **Add event** button on the right side of the screen and fill out the form! After this, your event will exist and show up in the app. To add more details, such as location, multiple communities, ### Advanced event management {% embed url="" %} Events look better in the app— and are more exciting to attend— with more information. Once you've created the event, select it in either the list or calendar view and expand the event. Once you're in the event page, you can add: * Location * Tags * Other communities you'd like the event to show up in * Host organization * Organizer (individual) * Images * Registration instructions * And more! You also can manage: * Event listing status * Is your event open to the public, private to an individual or group, or do you not want it to be listed in the app at all yet? We have settings for each of these scenarios * Registration * Make registration **open** (anyone who can see it can sign up), **closed** (signing up is not an option), or **locked** (registration status cannot be changed by users— if they have registered themselves or been registered by an administrator, they will not be able to unregister) ## Resources ### Opting into existing resources {% embed url="" %} To opt-in to an existing resource, find the resource in the Gather Resource Library and click to open. At the very top of the page, you will see a **Listed in communities** section. Click the **Add to community** button and select your community. That's it! This is also how to add a new resource that you may have made into the multiple communities within your app. ### Adding new resources {% embed url="" %} Adding new resources is incredibly similar to adding new events. Navigate to either the **Resource** or **Gather Resource Library** tabs. If you go to the former, select the community for which you'd like the resource to appear, and then press the add resource button, which will open a basic form. If done in the Gather Resource Library, the buttons in the upper right hand corner will work the same. Please note that if you do press the **Add private resource** button, it will reroute you into the first flow, where you must select the community before proceeding to fill out the form. After filling out the form, find the resource again via search, or if within a community, it will show up at the top of the **All** tab within that community resource page, as seen in the video. From there, use our AI content companion (or not!) to help you flesh out the resource details. The red error messages will indicate which items need to be filled in. ## Users ### Adding users {% embed url="" %} To add a new user— or an existing user to a new community— navigate to the **Add users** tab and press the button in the upper right hand corner. From here, a form will pop out. Select the app, the community the profile will be in, and the access role of the user. Then add their phone number, first and last name (or initials; data collection procedures are up to you!), and identify yourself as the referrer. Check the box if you would like an SMS to be sent to the user prompting them to download the app and sign in. Once you submit this form, our system will grant the user access to the app and community of your choosing. If the user already has an existing account with Gather (for example, they are enrolled in a different community already, or in another app) an **Already invited** badge will show up next to their invite. *This still grants the user access, but also confirms the prior existence of an account.* ### User management {% embed url="" %} Easily look into a user's community profile and account information by navigating to the Users tab on the sidebar and selecting the community the user is in. Then navigate using the role type chart or the search button. Delete a community profile or revoke community access from these user pages. ## Tags {% embed url="" %} Tags are essential for connecting users with the events and resources best suited to them. Although you can make new tags directly from an event or resource page, you can also explore existing options and create new private tags from the Tag Library. Tap on a tag to see all associated events and resources! ## Onboarding {% embed url="" %} The first thing your members will encounter after logging in is the onboarding flow. This is highly adjustable to your interests and needs as an organization. Onboarding is typically something the Gather team will help you set up prior to launch. However, having an understanding of how onboarding works in valuable for if you'd like to adjust the questions at any point. 1. First, go to the Community configuration tab and select the community of your choice. You should see a large button that says Onboarding survey at the top of the page. Click to enter the onboarding flow. 2. From here, you can name the onboarding flow and add pages. These pages can contain as many or as few prompts as you’d like. Prompts are text boxes or questions members will fill out within a survey page. 3. To add more prompts, click into the survey page. From here, you can add additional prompts. Prompts can be required or optional, and you can also attach user tags to them. 4. For example, a prompt might be “Do you need a job?” If that person selects the “Yes” option they will be tagged with a “Needs job” user tag. 5. Scroll down to the Options section and click to open an option (or hit “Add option” to add a different response). 6. When you open the option, you will see the Option title, responses from members, and the associated user tag/s. In this example, the user tag “Unemployed” is associated with the option “Yes” for the question “Do you need a job?” However, there are many other options, and you can always create new user tags specific to your community. The user tags can be made visible to administrators only, organizers and admins, or all app members. 7. Make as many or as few survey pages and prompts as suits your organization. If anything changes, you can always update the survey at a later time, as well as remove member responses to send them back through the flow if necessary. ## Content Configuration {% embed url="" %} 1. Navigate to the **Community configuration** tab on the sidebar, and then to the community you're looking to configure. 2. Scroll down to the section called **Tabs** 3. Select the Tab you would like to manage content within. The following page will appear from the side. ![As seen in the image, this is where you can pin specific categories to the home screen. We have auto-pinned the member’s upcoming events, but you have full discretion over what is pinned.](https://3024605654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu9PavPKMcvtJuywiEX1R%2Fuploads%2FjxS7NrUtPUrl1CBu5KkW%2Fextracted_image_1745350226-042.png?alt=media) 1. To make a new category, select the “Add category” button in the upper right hand corner. This will trigger the launch of a form. 2. You will put the category name, the type of content, and relevant features. Most importantly, you will add a filter to hone the content in that category, whether by those participating in an event, saved items, or via tags. 3. After you hit “Create,” you will be back on the opened Tab content page. Your new category will appear at the bottom of the list (hover and drag the 6 dots to reorder the categories). 4. Press to open. If you have not yet added criteria such as tags, the category page will look like this have a 'Hidden • Invalid' visibility status. ![](https://3024605654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu9PavPKMcvtJuywiEX1R%2Fuploads%2FN2qNptrZZbfRkzDzVm8X%2FScreenshot_2025-07-14_at_1.17.58_PM.png?alt=media) Once you have added the category tags, the category will become valid and visible. That’s it! When you close and reopen the app, you should see the content categories you created at the top of the Event, Resources, or People tab. ## Summary & End Notes You’ve done it! These functions are most of what you’ll be doing in the Admin Hub. There are more capabilities that you can develop over time as you become more comfortable with the set up. If you need more information on what a certain button does, or what a certain tab means, go to the Hub Glossary tab in this document. We’ve tracked and explained everything you might encounter in the Hub. If you have any questions, never hesitate to reach out to Gather Support. We can’t wait to see what you create! *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.joingather.org/admin-hub-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.