Documentation

Quick start

From sign-up to a working space in one evening.

1. On the login page choose “Create a church” → church name, your email and a password.
2. Confirm your email from the message we send. You become the owner — the role with full access.
3. You immediately get two spaces: the management console and a public site at <your-church>.alphaos.space.
4. The dashboard shows an onboarding card: “Set up the site”, “Add people”, “Share the QR”.
5. Fill in the site brief (the Site section), import your people and print the QR from the /links page.

How it works

Five ideas that make the rest of the docs make sense.

One dataset

The console, the public site and the /links page read one database. Change the schedule in the console and the site changes with it. There is no second store, so the two cannot drift apart.

Your church space

Your data is isolated from every other church. You own it and can export it at any time.

Roles and sections

What a person sees in the menu is decided by their role. Built-in roles: Owner, Admin, Pastor, Treasurer, Minister, Viewer. You can also create your own.

Who serves vs what happens

Team rotas answer “WHO serves this Sunday”; the service plan in the calendar answers “WHAT happens inside the gathering”. Two views of the same data.

Plans

Basic — church management; Standard — plus the public site and a custom domain; Pro — plus the AI studio. Your current plan shows at the top of the sidebar.

The console and navigation

Sections on the left, grouped exactly as they are in the access editor.

Overview

Dashboard and Reports.

People

One section with three tabs: People (and Families), Ministry teams, Small groups.

Planning

The calendar as a workspace (gatherings, events, rehearsals, small groups — as layers), Team rotas, Media plan.

Ministries

Worship, Kids ministry.

Church life

Meetings & minutes, Prayer, Tasks.

Money

Finance.

Materials

Library, Content, Presentations, Images, YouTube digest.

Site & forms

Site, Join form.

System

Settings (church, subscription, usage, reference lists, access).

Dashboard

The first screen: what needs attention today.

Counters

People, groups, ministries, balance for the month.

Needs attention

Pending applications from the site, new prayer requests, overdue tasks — one click away.

Cards

Next gathering, my tasks, upcoming events, birthdays this week, finance for the month.

Custom widgets

The set of cards is configurable — remove what your church does not use.

Reports

A church-wide summary for a period — for the board, members’ meetings and your own clarity. They live on the Dashboard under the “Reports” tab.

1. Pick a period at the top: “Month”, “Quarter”, “Year” or “Custom range” with two dates.
2. The page shows people and membership movement, attendance, serving and finance for that same period.
3. The “PDF” button exports the report as a finished document you can hand out.

People

Profiles, import, tags, membership stages, duplicates, statistics.

At the top: the section tabs (“People”, “Ministry teams”, “Small groups”). Inside “People” there is a single control row: the “People / Families” toggle, search, “List / Cards”, birthdays, “Import”, “Select” and “Add person”. Export and look-alike cards live under “⋯”. Below: stage chips (only the ones with people in them) and “Filter” with grouping and sorting.

The list is a table: columns “Person”, “Contacts”, “Ministries & groups”, “Stage”. Phone, Telegram and e-mail are clickable in the row itself; hovering reveals note, stage change and console access on the right. On a phone the row folds into two lines and the stage chips scroll sideways.

1. Add manually: “Add person” → name (required), gender, stage, phone, Telegram, email, date of birth, city, tags → “Add”.
2. Import: “Import” → drop an .xlsx/.xls/.csv (first row = headers) → map the file’s columns to fields → pick a default stage → “Import N”. The window itself explains the rules: columns are recognised by their names, dates and genders are normalised for you, the first five rows are previewed before anything is written, and existing cards are never overwritten — every row is added as a new person.
3. Bulk actions: “Select” → tick cards → in the bottom bar “Change stage…”, “Add tag…” or “Delete”.
4. Row quick actions (on hover): note, change stage, and console access. A green shield means the account exists (the tooltip names the role); a key means “Grant access” and opens the profile straight on the Account tab. Calling, Telegram and e-mail are right there in the “Contacts” column.
5. Export: “Export” downloads the current (filtered) list as CSV.

The profile

Tabs: Overview, Profile, Family, Serving, Notes, Account. Overview also shows that person’s attendance and serving statistics.

Membership stages

Profile → Overview → “Membership stage”: click another stage; the history is kept below. The stages themselves are edited in Settings → Reference lists — including the built-in ones.

Children

A separate category in the same chip row as the stages. Being a child is an age (under 18, from the date of birth), not a stage: stages describe an adult’s path, so children have none and used to disappear into the “no stage” pile. The “Children” chip shows every child, including those the church has already given a stage; the list still shows that person’s real stage. The category also works as a filter condition (“Stage = Children”).

Custom fields

Settings → Reference lists → “Extra profile fields”: “Add field” and a type (Text / Paragraph / Date / Number / Select).

Notion-style views

The “Filter” button above the list: conditions as rows “field → operator → value” (stage, tag, ministry, small group, age, gender, birthday month, marital status, baptism, member since, residence, contact, custom profile fields), all combined with “and”. Next to it — “Group by” (stage, ministry, group, age, gender, birthday month…) and the order (A→Z, newest, by stage, by age, upcoming birthdays). Any view is saved as a segment with “Save filter” and opens in one click.

Duplicates

When cards look alike by name, phone or email, a “Duplicates: N” button appears → choose the primary one (●) → “Merge”. Notes, giving and group membership move across.

Photo

Profile → Profile tab → “Upload photo” → “Save”.

Console access

Profile → Account tab → email + role → “Create and send”. With no mail configured, the system shows a temporary password.

Finding a person

Everywhere a person is picked (an item owner, the host, the preacher, baptisms) the search is the same: words in any order, a phone matched by its digits whatever the formatting, e-mail and Telegram, and even text typed on the wrong keyboard layout.

Families

People → the “Families” toggle. Households with real relationships.

1. Create: “New family” → a name (e.g. “The Kovalchuk family”) → “Create”. The card opens straight away.
2. Add people: “Add to family” → pick a person and a role (Husband / Wife / Child) → “Add”.
3. A child who is not in the database yet: “Add a child not in the database” → name, date of birth, gender → “Create and add”.

Small groups

Membership, attendance, a public catalogue and sign-up by link.

1. Create: “Add group” → name, category, day, time, capacity, location, description → “Create”.
2. Members: open the group → “Members” → “+ Add person…” and a role (Leader / Member) → “Add”.
3. Attendance: the “Attendance” tab → pick a date → “Record meeting” → who was there, the topic, guests → “Save”.
4. Public sign-up: switch the group to show on the site and it appears in the /groups catalogue. “Invite link” gives a personal /g/<code> link for guests.
5. Requests: the requests tab is the queue — “Approve” adds the person to the group (creating a profile for a new guest), “Decline” leaves a trace in the log.

Ministry teams

Teams, positions, leaders and what each person can do.

1. Create: “Add ministry” → name (e.g. “Worship”), team kind, description → “Create”.
2. Positions: the “Members” tab → “+ Position” (Vocals, Sound, Coffee, Teacher…). Positions are what people get assigned to in the rota.
3. People: tick a person for a position and they join the team. The star in a row makes someone a leader.
4. Dates are scheduled in “Team rotas”, not here.

Calendar and service plans

One workspace: month, week or list. Clicking a day opens the day panel with everything in it.

1. Click a day → the day panel: the service plan with timings and the end time, who serves, the rehearsal, events, small groups, plus what goes out in media that day (publications are created in the Media plan, not here). ← → arrows step through days, Esc closes.
2. Create: the “Create” button at the top, or the same two actions in the day panel — “Gathering” (order, people, songs) or “Event” (for the site and the calendar). If the church has plan templates, you are asked which one to start from.
3. The plan is edited on top of the calendar: “Edit” in the day panel → items from the “Add:” row (Welcome, Worship, Prayer, Sermon, Communion…), drag by the ⋮⋮ handle, owners, durations → “Save changes”. “Back to the day” returns to the same day.
4. Layers above the grid (Gatherings · Rehearsals · Events · Small groups) are the filter: a click keeps ONLY that layer, clicking it again brings them all back, Alt+click adds or removes a layer. The choice is remembered.
5. The “List” mode has a horizon: this month, the next 3 months or the past 3 — the former “Upcoming” and “Archive” of plans.
6. Copy to another date: in the editor “Copy to date” → “+1 week” / “+2 weeks” / “+4 weeks” or a specific date → “Create copy”.

Draft or final

A draft has a dashed outline in the grid, a final one is solid. In the day panel the status sits next to the title.

On the site

The “on the site / not on the site” chip in the day panel publishes the gathering to the church website or takes it down. New gatherings are published right away — including those created from the rota.

Attendance

A past gathering shows a “How many people came?” field in the day panel — the number is recorded in place. The full record lives in the “⋯” menu → “Attendance”: pick a gathering that already happened, then enter how many came, how many were new and children, how many made a decision and how many were baptised. People ticked there get the baptism date on their own profile.

The “⋯” menu

Plan templates, attendance, monthly themes, service-plan images, the public events page.

Moving

Drag an event or a gathering to another day, or change the date with the field next to the event in the day panel. A recurring event asks about the whole series.

Team rotas

WHO serves on which dates — one table for the whole quarter.

1. The “All ministries” tab shows the whole Sunday at once: preacher, theme, passage, duration. “+ another sermon” adds a second one to a date.
2. No dates yet? “Create Sundays (N)” generates empty gatherings for the whole selected period. The weekday comes from your own gatherings — a Saturday church gets Saturdays.
3. Per-team tabs (“Worship”, “Kids”, “Tech”, “Other ministries”) — people on positions, clashes, invitations.
4. A position that is never scheduled for a gathering (an editor, an archivist, a page admin) carries an “in the rota / off-gathering” chip in the team roster. “Off-gathering” keeps it in the team and in people’s skills, but takes it out of the rota grid and out of the “missing N” count. The same exists for a WHOLE ministry: the ministry card → “Settings” → “Scheduled for gatherings”. Untick it for outreach or admin teams and they leave the Sunday rota without losing their roster.

Confirmations

A minister sees their assignment in “My serving” and confirms or declines it with a reason. You see who answered and who has not.

Unavailability

Anyone can mark dates they are away; the planner routes around them.

Monthly cap

Each person’s card sets how often they may be scheduled and the minimum gap between turns.

Sermons

Team rotas → pick “Sermons” in the “Planning” list. This is where they are planned: who, when, theme, passage, minutes and the host.

1. Pick a horizon: the next 3 or 6 months, or the past 6.
2. Each gathering is a row: date, title, status, preachers with theme, passage and minutes. Gatherings without a preacher are highlighted — those are the gaps.
3. “Rota” opens that date in “All ministries”, where assignments are made; “Plan” opens the gathering itself.
4. On the right — preachers over 18 months: how many times, when last, whether already scheduled ahead. Click a person to keep only their gatherings in the list.

Events and registrations

An event is what visitors of the church site see; registration (RSVP) comes from the site.

1. Add: “+ Event” above the calendar or “Event” in the day panel → name, category, colour, date, time, location, description.
2. Turn on “Registration (RSVP)” and “Show publicly”; with registration set a “Capacity” (blank = unlimited) → “Create”.
3. Registrations: open the event → the “Registrations” tab → “+ Add” (someone from your list or a guest). “Mark attended” sets the status, “CSV” exports the list.

Media plan

A content calendar for the media team: what goes out, and when.

1. Pick a month at the top — the grid shows what is planned, day by day.
2. Click a day → a new entry: kind (Post, Story, Reels / Shorts, Video, Announcement, Banner, Podcast, Other), channel (Instagram, YouTube, Telegram, Facebook, TikTok, Site, Other), topic, owner.
3. Filter by channel to see only what goes out on, say, Instagram.

Music ministry

Your church songbook, a shared catalogue of 40,000+ songs, and analytics.

Songbook

Your church’s songs: lyrics, chords, key, tempo, themes, links to video.

Shared catalogue

Over 40,000 songs with chords. Found one — add it to your songbook in a click.

Analytics & CCLI

What you sang and how often over a period — exactly the numbers a licensing report needs.

1. A song card: “Chart” — lyrics with chords; “Details” — key, tempo, themes; “Links” — video and tracks; “History” — when you sang it.
2. Transpose: change the key and the chords follow. Capo and the Nashville number system are both supported.
3. The setlist for a gathering is built in Team rotas → the “Worship” tab: “+ song” right in the cell for that date.
4. The band gets one PDF with the charts for the whole setlist.

Songs to learn

In “Team rotas” open a rehearsal (the time button) → the “Songs to learn” block → “Add a song”. The song does NOT enter the service plan or chart pack — but the whole team sees it in “My serving” right away, with video and materials. Once learned, remove it or add it to a real setlist.

Kids ministry

Age classes, rosters, lessons and attendance.

1. A class: name, age range (“from 3 to 6”), room, teachers. The system warns when there are too few teachers for the number of children.
2. Roster: children come from the People section — including those entered in families as non-members.
3. A session: date, topic, a link to the lesson material, attendance.

My serving

A minister’s personal screen — available to everyone who signs in.

My rota

The dates you serve, with position and team.

Confirm / decline

One button. When declining, give a reason — the leader sees that, not a bare refusal.

My unavailability

Mark the dates you are away and the auto-planner routes around them.

Songs and plan

The setlist and the service plan for your date — no digging through chat history.

My teams and my small group

Where you serve and which group you belong to.

My votes

Open church votes you are eligible for.

Meetings, minutes and voting

Agenda, quorum, minutes and secret member ballots.

Two tabs: “Minutes” (for those who run meetings) and “My votes” (for every member).

The meeting page follows the clock of the meeting itself: who came → recording → agenda and decisions → action items → summary → approve. A strip at the top says where you stand and what to do next. An approved set of minutes is shown in a different order — as a document, starting from the summary.

1. Create a meeting: date, kind, chair, secretary. For a team meeting pick the “Ministry” — the meeting is then tied to that team. The minute number is assigned automatically, numbered per year.
2. Who came: the list is the whole audience of the meeting. Three states, not two: “present”, “no” and “not marked yet”. Marks travel one at a time, so the same meeting can be marked from the console and from a phone at once.
3. Quorum: the system snapshots the audience at the moment the meeting is created and computes quorum from it. Later membership changes do not rewrite quorum retroactively.
4. Recording (Pro): “Record the meeting” → allow the browser to use the microphone. The recording splits itself into parts, the text appears while the meeting is still going, with speakers separated, and the audio file is deleted once transcribed. Already recorded on a voice recorder — “Upload a recording”.
5. Draft: “Draft the minutes” → AI shows a summary, the items with decisions and the list of action items. “Move into the minutes” appends the items and puts the action items on the task board.
6. Agenda: an item is one topic — what was discussed and what was decided.
7. Voting: inside an item — “put to a vote” → question, options and “Who votes” → “Open”. Once closed, the result lands in that item’s decision by itself.
8. Action items: from any item — “make it an action item”: a person from the list and a date. The task goes to the shared board and stays tied to the minutes.
9. “Approve minutes” at the bottom of the page freezes the document. It needs at least one item and no unsaved changes.

Secrecy

A ballot is stored WITHOUT any link to a person. Only turnout is recorded separately. Reconstructing who voted how is impossible, even with database access.

Results

Hidden while the vote is open. On close, the outcome is written into the decision text of that agenda item.

Frozen minutes

Approved minutes cannot be edited by ANYONE — the owner included. To change them, they must be explicitly reopened, and that action is logged.

Who votes

Eligibility follows the membership stage — guests and newcomers are not on the ballot. For a group vote, ballots go only to group participants who are church members.

The AI draft

AI never writes anything into the record by itself: the secretary reads the draft and carries it over. Minutes are a church document, and a person answers for every line.

Notices

What the church itself needs to read: a changed hall, a camp collection, a thank-you to the team.

The word “announcement” shows up three times in this system, and they are different things. In a service run sheet it is an item someone will say from the front. In the media plan it is a post that will go out on social media. Here it is a message to your own people: those who open the console read it, and it is published nowhere.

1. “Notices” → “+ Notice”. Often the headline is enough: “Sunday gathering in the small hall”.
2. The body is optional. It is for the detail: why, until when, who to talk to.
3. “Shows until” is the date after which the notice disappears on its own. This is the important field: without it the board turns into an archive within six months, and fresh news sinks in it.
4. “Pin to the top” is for what has to stay in front of people longer than its turn.

Who sees it

Everyone the church has opened the “Notices” section to. Writing needs the edit right.

On the dashboard

The three latest notices sit in a widget on the home screen. With no notices the widget is not drawn at all — an empty card is not news.

Archive

An expired notice leaves the list, not the database. The “Archive” tab shows what was announced earlier.

Prayer

Requests from the community and from the public form on your site.

Two tabs: “New” and “Archive (prayed for)”. On a card: “Prayed for” (moves it to the archive), “Back to new”, “Delete”.

Kinds of prayer

A one-off request, a standing prayer (something prayed over for months) and thanksgiving. A one-off goes to the archive after “Prayed for”; a standing one stays on the list until God answers.

“God answered”

The button is on every prayer. Pressing it lets you record the TESTIMONY — how exactly God answered. The whole team sees it next to the request: the prayer list becomes a history of answers, not just a queue of asks. The field may be left empty — the prayer is then simply marked answered.

Group prayers

A small group keeps its own prayer list inside its section. The leader can move a request “To the church list” — then the whole church sees it, tagged with the group.

Surveys

Feedback from people: how the gathering went, how the congregation is doing.

A church learns how people are doing in two ways: someone comes up and says so, or the pastor guesses. The first only works for people who know how to come up. A survey adds a third way: you ask the questions, anyone may answer, and answering costs no one a face-to-face conversation.

1. Create: «Surveys» → pick a ready-made one («After the gathering», «Congregation health check») or «Blank survey». Questions in the ready-made ones are already written in the person’s own voice, not the church’s.
2. Review or change the questions on the «Questions» tab: scale, NPS score, single choice, multiple choice, yes/no, free text. Any question can be made optional.
3. Press «Open» — only then does the link and QR code appear. While the survey is a draft, there is no one to answer it.
4. Share it: copy the link, show the QR on screen, or tick «Show a button on the church site».
5. Read the «Responses» tab: average, distribution and the full texts. When you have enough — «Close».

Anonymous

If a survey is anonymous, the link to the person does NOT exist in the database: we do not hide it in the interface, we do not write it. That is why a survey cannot be switched to non-anonymous once the first response arrives — a promise people have already answered under cannot be changed after the fact.

Who it is for

«Public» — the link may go on the site; «Members» — send it to your own people. The health check defaults to members: it asks about trust in leaders, and that does not belong on a front page.

Comparing waves

Repeat the same survey six months later and an arrow appears next to each number showing the change since last time. Questions are matched by their wording, so do not rewrite them between waves if you want to see the trend.

Form protection

The public page is protected by a captcha and a limit on responses from one address. No sign-in is required to answer — deliberately: the after-gathering survey is also filled in by a guest visiting for the first time.

Tasks

A kanban board: To do / In progress / Done.

1. Create: “+ Task” → what to do, description, status, priority, assignee, due date, a link (ministry, group, event, service plan, person, meeting) → “Create”.
2. Drag cards between columns. Moving to “Done” stamps the completion date.
3. Tabs above the board: “All” — the whole church, “Mine” — everything assigned to you across ministries, then your ministries as separate lists; any other ministry is in the dropdown. A task belongs to a ministry through the “Ministry” link on the card; “+ Task” inside a ministry tab sets that link for you.

Money requests

Finance → the “Requests” tab. A minister asks for funds; the finance team decides.

Requests live inside Finance as their own tab. Who sees it is set by the role’s money level: “Money requests only” gives exactly that tab and only the person’s OWN requests (a ministry leader asks for camp money without seeing the church accounts); “Full” sees the whole queue with decision buttons.

1. Submit: “Submit a request” → what the funds are for, the amount, needed-by date, ministry (optional) and the reasoning → “Submit”.
2. Line items: break the total into rows — “Venue 3 × 1500”, “Food 4000”, “Transport 1500”. The request total is computed from the rows, so you do not enter it separately.
3. Decision (finance role): “Approve” — you may enter a smaller amount than requested, with a comment; “Decline” — a reason is required and the requester sees exactly that.
4. Payout: on an approved request press “Pay” → account, expense category, date → “Pay and record the expense”. An expense “Money request: …” appears in Finance immediately.

Approved ≠ paid

A decision is a promise; money leaves the account only via “Pay”, and that is what writes the real expense to the ledger. The requester sees the honest state: approved but not yet received.

Withdrawing

While a request is pending, the requester can withdraw it. After a decision — no: the trace must remain.

Who sees it

Settings → Access → role → finance level. “Money requests only (own)” grants the Requests tab and nothing else; the built-in “Minister” role has exactly that.

Finance

Tabs: Overview, Income, Expenses, Accounts & currencies, Donors, Funds, Categories & budget.

1. Accounts & currencies: “+ Account” (name, currency, type, opening balance). “+ Currency” adds a new one (code and symbol).
2. Base currency: the “Base: {code}” button → the new currency and a conversion rate. Every amount is recalculated.
3. A transaction: “+ Add income” or “+ Add expense” → account, amount, rate (for foreign currency), date, method, fund, donor (for income), category. You can “Attach a receipt / document” (up to 6) → “Save”.
4. Line items in one operation: the “Items” block under the form — break the receipt into rows and give each row its OWN category. The operation total is computed from the rows; the “Amount” field becomes that total.
5. Annual budget: “Categories & budget” → “Create budget” → pick the year and a starting point (blank, last year’s actuals, a copy of another plan). Then add categories with a yearly amount — income as well as expenses.
6. Amount or percentage: the ₴/% toggle on a plan row lets you set a category as a share (“10% to missions”): the amount is computed from planned income and recalculates when the income plan changes.
7. Monthly split: the calendar button on a budget row → enter amounts per month (“Evenly” / “Like actuals” are ready-made). Put heating on winter, camp on summer.
8. To have the plan compared with actuals in the Overview, press “Make active” — exactly one budget is active at a time.

Transfers between accounts

“Accounts & currencies” → “Transfer between accounts”. Cash → bank, local currency → a foreign account. It counts as neither income nor expense. When the currencies differ, enter the amount that actually arrived per the bank statement — the bank uses its own rate. The fee is a separate field and is recorded as a real expense.

Why items carry categories

One shop receipt is often two budget lines: snacks for the kids ministry and cleaning supplies for the hall. Without a breakdown the whole sum landed in one category and quietly ate another ministry’s budget. With items, the Overview, the annual budget and the Reports all split it the same way — to the penny.

Plan vs actual

The budget screen compares actuals against the plan TO DATE, not against the yearly figure: in March a yearly comparison means nothing. Next to it is the year-end forecast: actuals so far plus the plan for the remaining months.

Off-plan

Spending in categories that are not in the plan, and spending with no category at all, is shown in a separate block. One click adds it to the plan.

Campaigns

The “Funds” tab → “+ New fund / campaign” → set a “Goal” and the fund becomes a campaign with progress, dates, percentage and donor count.

Transfers between funds

In “Funds”. Money moves between funds and counts as neither income nor expense — otherwise the same sum would double your turnover.

Reports

Overview → a period → “PDF report”. Donor statements: “Donors” → open a donor → pick a year. The donor list exports to CSV.

Google Sheets

“Income” → “Google Sheets” → paste the link (sharing set to “anyone with the link”) → map the columns → “Import”.

Duplicates

If a new income entry looks like one already recorded (same date, amount, donor), you are warned before saving.

Library

A shared store for notes, outlines and church documents.

1. Create a note, give it a title and write in the full-size editor. The author and date are kept.
2. Attach files — an outline, a rota, a scan of a document.
3. The “Bible study” button opens a separate tool (below).

Bible study

Library → “Bible study”. It equips you to study, it does not write your sermon.

1. Pick a mode: “Step-by-step study” or “Compare translations”.
2. Study: a reference (e.g. “John 3:16”), a translation → “Start study”. In the chat: “Next thought”, “Original word”, “Cross references”, “Outline”.
3. Save the result to the Library or turn it into a presentation.
4. Compare: a reference plus up to 5 translations → “Compare” (verse by verse) → “Explain the differences (AI)”.

Content

A generator for posts, announcements and invitations in your church’s voice.

1. Choose the type: Post, Announcement, YouTube description, Invitation or Sermon outline.
2. Describe the topic and press “Generate”.
3. The result can be copied or sent to the Library. Everything lands in “Generation history”: click to reopen, “Generate” for another take, the bin to delete.

Presentations

From a sermon text to designed slides, with export and projection.

1. Paste the sermon text or a theme → “Generate slides”. The design follows your site’s style.
2. Edit by hand: the pencil on a slide card → type (Points / Verse / Quote), heading, thought cards (up to 4), verse, quote. Arrows reorder; “Duplicate”, “Delete slide”, “Add slide”.
3. Or describe the change in words in the “Edits to the deck” bar → “Apply” and the AI rebuilds it.
4. “Illustration” adds an AI image to a slide. Export as “PPTX” or “PDF”; “Full screen” projects it.

Images

A logo, hero photography and illustrations.

1. Choose a type: “Preview (for posts)”, “Photo for the site” or “Edit a photo”.
2. For editing, upload the photo. Describe what you need → “Generate”.
3. Copy the URL or open the result; everything is kept in the “Gallery”.

YouTube digest

A sermon summary from a video.

Paste a video link — the system reads its captions and produces a structured digest: themes, key thoughts, passages. Save it to the Library or hand it to Content as the basis for a post.

The site brief

The first screen of the Site section: 8 steps that make the site yours rather than a template.

Until the brief is complete, the rest of the Site section stays closed. That is deliberate: a site generated from a single “describe your church” box comes out the same for everyone — the model has nothing to tell churches apart with.

1. About the church

City, tradition, founding year, size, schedule, address, socials (from any country, not just our list) and site languages.

2. Who the site is for

Who you most expect, in order of priority, and the one action the whole page leads to.

3. How you sound

Tone of voice, a sample of your own writing, what to avoid, and whether to name the pastor.

4. Look and references

Mood, logo and brand book, brand colours and up to three reference sites with what exactly you like about them.

5. Site blocks

What belongs on the page — and, crucially, a description for EACH chosen block: “Testimonies” in general and “three families who came back from abroad” produce different sites. You can add blocks of your own.

6. Photos and materials

Up to 8 of your own photos, tagged with what they show, or permission to generate imagery.

7. In your own words

The most valuable part: what no checkbox can hold.

8. Read the brief back

The brief is shown in full — exactly as the AI will read it.

The public site

The Site section. “Save & publish” applies your changes.

1. Style: the “Branding and home page” panel → “Site style” → a preset (Classic, Elegant, Modern, Bold, Calm, Editorial).
2. Logo and colour: “Generate” (AI) or “Upload”; set the accent colour.
3. Hero background: “Bring the site to life (logo + background)”, “Generate (AI)”, “Upload”, “Adapt with AI”, or a ready stock photo.
4. Text: tagline, hero heading and subheading, “About us”. Below: “Ministries”, “Our vision”, “Schedule”, “Links and contacts”, “/links buttons”, “Giving”.
5. “Save & publish”, then “Open site”.

Site sections

A chat tab: describe in words what a block should be, and the answer is already live on the site — nothing to save.

Layout review

The AI walks the finished site and checks it on desktop, tablet and phone: heading length, colour contrast, empty sections, missing contact details.

Languages

Your church site can be shown in Ukrainian, English, Polish, Spanish or Portuguese.

Your church domain

Site → the “Domain” tab. The subdomain is free forever; a custom domain is connected or bought here.

From sign-up your site lives at <your-church>.alphaos.space. That is a real, permanent address you can use for years. A custom domain (say mychurch.org) is for when the church wants its own brand in the address bar.

Your domains

The table at the top of the tab: address, kind (subdomain / custom / bought through us), status, cost and the date it is paid up to. It is the one place that shows everything at once.

1. Already own a domain? In the “Custom domain” block enter it (e.g. mychurch.org) → “Connect domain”. Connecting is free.
2. The system shows two DNS records — a CNAME and a TXT — each with a copy button.
3. Open your registrar’s control panel (wherever you bought the domain), go to DNS and add both records exactly as shown.
4. Come back and press “Verify”. The status moves from “Waiting for DNS” to “Active”. That usually takes minutes, occasionally a few hours while DNS propagates.
5. No domain yet? In “Register a domain” type the name you want → “Check”. For an available domain you will see the yearly service fee and a term (1, 2, 3 or 5 years) → “Order”. After payment we register the domain for your church and connect it to the site.

What it costs

Connecting a domain you own is free; you pay your own registrar for the domain itself. For a domain registered through us, the exact service fee and renewal date appear in the “Your domains” table.

Renewal

Once a year. Thirty days before the date we issue an invoice and email you — early on purpose, so there is slack: paying on the last day risks the domain going down before the payment clears.

The subdomain stays

After a custom domain is connected, the alphaos.space address keeps working — printed QR codes and old links do not break.

Who can do this

Only the Owner or an Admin can connect, order or remove a domain.

Which zones

Ukrainian ones — .com.ua, .org.ua, .kiev.ua, .in.ua — and international: .org, .com, .church, .info and more. A bare .ua can only be registered by a trademark holder, so we handle those by hand — just write to us.

Join form

A builder for the public /join form.

1. Add a field: “Add field” → label, section, type (Text, Phone, Email, Date, Paragraph, Select, Buttons), options for selects, and the “Required” / “Full width” / “Visible” switches.
2. Order with the ↑/↓ arrows inside a section. The switch hides a field, the pencil edits it, the bin deletes it (your own fields only).

Children on the form

The form has a “Children” block: each child’s name and birth date. Children from an application become profiles right away and join their parents in a “<Surname> family” household.

No duplicates

When both parents apply, a child is recognised by name and birth date — no second profile is created. A teenager who applied on their own is linked to their existing profile too. If the names match but birth dates are missing, the system does NOT decide by itself: it creates the profile with a “possible duplicate” note, and a person makes the call.

QR and the /links page

One code for everything the church has online.

Your church has one public hub page, /links: the site, socials, the join form, giving and your own buttons. Point the printed QR at it, and a banner printed last year stays current — you change the links in the console and the code stays the same.

Buttons

Site → the “/links page buttons” panel: label, caption, URL; order with arrows.

Socials and giving

Pulled in automatically from the “Links and contacts” and “Giving” panels.

Roles and access

Settings → the “Access” tab (Owner / Admin).

1. Grant access: “Invite user” → pick someone from People → email and role → “Grant access”. An email goes out (or the system shows a temporary password).
2. Custom roles: the “Roles and access” panel → “New role” → name, which sections it sees, the finance level, whether it can edit → “Create role”.

Section grouping

Sections in the role editor are grouped EXACTLY as in the sidebar. That matters: there used to be two groupings, so an owner granted access in one mental model while a minister looked for the section in another.

Finance is separate

Money access is not a “section” but its own level: none / totals only / full. A pastor can see the balance without seeing who gave what.

Managing users

In a user’s row: change role, reset password, disable access, delete the account.

Activity log

The “Activity log” panel: who did what, and when.

Reference lists

The “Reference lists” tab: membership stages, roles in groups and ministries, extra profile fields.

One email — several churches

The same email can have access in several churches (e.g. someone serving in two congregations). On login the system asks which church to enter, and you can switch anytime — via the selector under the church name in the sidebar. One password covers them all.

Data security

Church data is sensitive — so here are specifics rather than reassurance.

Encryption

In transit — TLS/HTTPS; at rest — at the Cloudflare infrastructure level.

Passwords

Never stored in the clear — only a cryptographic hash (PBKDF2). Not even we can recover a password; it can only be reset.

Church isolation

Each church’s data is separated from every other on every request.

Form protection

Public forms (join, prayer, group sign-up) are protected against automated abuse by a captcha and rate limiting.

Backups

Taken regularly.

Personal data

Photos of children, private phone numbers and addresses, giving amounts and names from prayer requests never reach the public site.

Plans, trial and billing

Settings → the “Subscription” tab.

Free trial

14 days free at the Standard tier — no card. So during the trial you have both church management and the public site.

Basic — $39/mo billed yearly ($49 month-to-month)

The whole management system: people, families, groups, ministries, team rotas, service plans, worship, kids, meetings and voting, finance, events, tasks, roles.

Standard — $64/mo billed yearly ($80 month-to-month)

Everything in Basic + the public site, a custom domain, QR and the /links page, AI site generation.

Pro — $99/mo billed yearly ($124 month-to-month)

Everything in Standard + the AI studio: content, presentations, Bible study, YouTube digest and 100 AI images a month.

1. Change plan: Settings → “Subscription” → “Upgrade” or “Downgrade” on the plan you want.
2. Billing period: the “Yearly” / “Monthly” toggle. The prices we quote everywhere are the yearly ones (−20%); month-to-month costs more but commits you to nothing.
3. Cancel: the “Cancel subscription” button. Access continues to the end of the paid period.

Your data

The data belongs to your church — and each person sees their own.

People export to CSV via the “Export” button, finance to PDF reports and CSV, donor statements per year, event registrations to CSV. Your own name and password are changed in Settings → “Church”.

“My data”

The first tab of Settings, available to EVERYONE with an account — no administrative rights needed. It shows everything the church stores about you: your profile, form answers, groups, family, attendance and YOUR own giving (nobody else’s giving is visible without a finance role).

“Something off?”

Below the data there is a “Report” field: write what to correct and the administration gets a task. A person changes the data, not a form — so the record keeps a trace of why it changed.