Changelog

Everything we ship — new features, fixes and performance improvements, newest first. No account needed to read this page.

72 changes · updated Oct 26, 2026 · this build: 1.7.0

1.7.0

Oct 26, 2026 · 13 changes
New

The last three emails look like Ekklesia too

  • The welcome, the confirmation you receive after changing your password, and the notice that tells you your account is locked were still plain Arial text with no mark and no footer — the only emails left that did not look like they came from us. They now use the same page as every other message we send.
  • Each says only what it is for. The welcome points at the sign-in page. The reset confirmation is a receipt with nothing to click, because there is nothing to do. The locked notice gives the three steps that actually unlock an account: choose Forgot Password, open the email, set a new password.
  • The reset email no longer suggests turning on two-factor authentication. We do not offer it yet, and a security email should not recommend a feature that isn't there.
New

The pages you reach when something has gone wrong

  • When the platform is closed for maintenance, or when a page is not yours to open, you used to land on a bare message inside the admin frame. Both now use the same sheet as the rest of the public pages: what happened, what it affects, and one way forward.
  • The maintenance page names the surface that is down, when it started, and that no data has been lost; it also tells you plainly when the mobile app is unaffected, so an admin does not assume the whole platform is gone. Its button re-checks, and signs you out if you would rather leave.
  • The page for a page you cannot open now says which of the real reasons applies — your role, a missing permission, a satellite church reaching a parent-church page, or a feature this workspace does not have. None of them offers an upgrade, because there is nothing to buy.
New

An invitation has a page of its own

  • Opening an invitation link, joining with a code, and the screen after you join were three different-looking pages. They now share one sheet, so a person who has never seen Ekklesia meets the same page whether they were invited by email or handed a code on paper.
  • The invitation shows who invited you, to which church, and what the link will do before you accept it. A link that has expired, been used, or belongs to another church says so plainly and offers the way to ask for a new one, rather than failing after the click.
  • The same page carries the set-password step, so a new member stays in one place from the link to their first sign-in.
New

The long pages are readable now

  • The terms, the members' terms, the privacy policy and this changelog were set the way the app sets a dense screen: a narrow column, heavy headings, and a contents rail that scrolled inside itself. They are documents people read, so they are now set as documents — one measured column, a serif heading, and links that look like links.
  • The changelog keeps its filters and its release groups, but the labels are sentence case rather than shouted, the entries are rows rather than cards, and the version you are reading sits at the top of the page instead of inside the text.
  • Nothing about what the pages say changed. Only how they read.
New

Our emails look like Ekklesia

  • Every email we send — the approval, the decline, the usage warning, the invitation — used to be built from its own colours, its own type and a blue that belongs to no part of this product. They now share one page: the mark, a red rule, a serif headline, sand for the details, and an ink footer.
  • The email carrying your sign-in code was the last one that did not use the layout at all: it was plain text assembled in code, which is why it was the only message a new member received that did not look like us. It is now a template like the rest, and the code is the largest thing in it.
  • No email mentions a plan, a price or an upgrade any more, because there are none. The emails that existed only to describe a plan have been removed rather than left to send something untrue.
New

Ekklesia is free. There is nothing to buy.

  • Plans, prices, trials, payment proofs and the approval queue are gone. A church gets the whole product — announcements, events, giving, merchandise, reports, the member app — without a card, a quote or a sales conversation. There is no feature held back for a higher tier, because there are no tiers.
  • Signing up used to end in a payment step and a wait for a reviewer. It now ends with a working workspace: the church is created, its first administrator is you, and the first thing you see is the panel rather than a status page.
  • Existing churches are unaffected. Nothing was taken away, no data moved, and the billing screens that remain are the records of what was paid before, kept because deleting financial history is not a thing we do.
New

Setting up a church takes one form, not a funnel

  • Creating a church used to be four steps with a plan choice in the middle. It is now a single short form — the church, then you as its administrator — and the review step simply confirms what you typed.
  • Your email is verified with a six-digit code inside the form, so the address that will receive the church's mail is proven before the workspace exists. The code boxes sit where the form expects them rather than centred under the field.
  • The button that creates the church stays disabled until you have accepted the terms for churches, the terms of service and the privacy policy. One switch, three documents, all named — the form no longer tells you the terms were not accepted after you have already clicked.
New

The public site, rebuilt around one sentence

  • The home page, the support page and every page behind them were carrying three designs at once. They now share one: a paper ground, a serif headline, one red, and real screens of the product instead of illustrations of it.
  • The first screen says what the thing is and what it costs in the same breath — Ekklesia, free for every church — because those are the two questions a visitor arrives with. Supporting the work is still there, and still separate from a church's giving: it is a page you can choose to visit, not a step in the product.
  • The pages are also lighter. The opening animation that could leave the page blank is gone, and the copy is shorter everywhere it was repeating itself.
New

Members can see their events by what they are part of

  • The member app's events list now answers the question people actually ask — what am I doing, what have I said yes to, what is coming — with tabs for upcoming, mine, and the events a member has registered for, instead of one long list.
  • Each tab is a real page of results from the server rather than a filter applied after everything has arrived, so a church with a full calendar opens as quickly as one with three events.
  • The old way of asking for every event still works, so a link saved before this change does not break.
New

A satellite church can use its parent's payment methods, or its own

  • A satellite church used to inherit its parent's GCash and bank details with no way to say otherwise, which is wrong the moment a satellite holds its own accounts. It can now keep the parent's methods or set its own, and the choice is visible on the payment settings page.
  • A channel that is already in use can no longer be switched off and re-offered at the same time; the page disables it and says why. The QR image is optional again — a church that only has an account number can save the method without one.
New

You can limit how many people an invite code admits

  • An invite code used to be bounded only by time: it stayed usable until it expired, and anyone holding it could join. Beside the expiry you can now set a maximum number of people the code will admit — the first few through are let in and the code then stops, whichever of the two limits it reaches first.
  • Someone trying a code that has run out is now told plainly that it is no longer usable and to ask the church for a new one. Until now the same message also covered a code that never existed and one that had been switched off, so a member holding a superseded code was told to check for a typo rather than to ask for a new one.
  • The limit is set on the Invite Code page, beside the expiry that was already there, and the page now says in plain words what the code will do — "Only the first 5 people can join with this code", or "Unlimited uses" — instead of a line that would have become untrue the moment you set a cap.
New

A welcome video sits under the home page's opening

  • The public home page now opens with a short animated welcome from the team, just below the hero and above the walk-through of how your church runs.
  • It does not start on its own: the clip carries a music bed, and a browser will not let video that makes sound play by itself, so it rests as a still frame with a "Watch the welcome" button and plays when you ask it to. Read on and nothing moves.
  • It is kept off the page's first load, so the home page is no heavier to open than before, and once you have watched it your browser keeps it rather than fetching it again.
New

You can see what your members have agreed to

  • When someone joins your church, accepts an invitation, or signs up, they now have to agree to the Terms of Service and the Privacy Policy before their account is created — and we record it: which version of each document, and when. Your church's own acceptance of the Terms for Churches is recorded the same way when your church is created.
  • The records are on a new Legal acceptances page, showing your church's record: the document, its version, who agreed and when. It answers the question a church is actually asked — "what did this person agree to, and when?" — which a checkbox on its own never could.
  • The documents are now published with their version beside the date, so you can see which one you are reading and which one you agreed to.
  • If a document is ever changed in a way that affects your rights or how your data is handled, you will be asked to accept the new version at your next sign-in rather than it passing silently. Routine edits that change nothing important will not ask you again, so agreeing stays something you mean.
  • Accounts created before this change are not asked to accept anything retrospectively, and nothing appears against them — we show absence as absence rather than assuming an agreement nobody made.

1.6.0

Oct 10, 2026 · 1 change
New

Members can ask to serve, and you decide

  • Until now the only way someone became a volunteer was for an admin to put them there, which is not really volunteering. A member can now ask to serve from the event in the mobile app, and the request appears on that event's Volunteers tab — with what they would like to help with and when they asked.
  • You approve or decline each one. Approving puts them on the roster for that occurrence and records the ministry they will serve in, so you can accept the one they asked for or choose another they are eligible for. Declining asks you for a reason, because the member is shown it.
  • Both decisions reach the member in their in-app notifications and on their phone; neither sends email. A member can withdraw a request while it is still waiting, and nobody is told when they do.
  • Only a member of your church can ask, and only for a ministry the event actually needs. A follower, a visitor, or a member with nothing to do at that event sees no button at all, rather than a refusal.

1.5.0

Oct 10, 2026 · 3 changes
New

The Invite Code section is available to every admin

  • Invite Code is now its own permission, granted to every admin role, instead of riding on the settings permission. It sat behind a check that no assignable role passed, so the section was visible only to the platform operator and read as missing for everyone else.
New

Every admin page and every action now checks its permission

  • Twenty-five pages had no check at all: an admin who could not see a link could still type the address and use the whole page. Every page is now checked before it opens.
  • Actions inside a page are checked before they are offered, so the panel no longer paints a button the API will refuse and then report as an error after you click it.
  • Four read permissions were added, so a role can be given read-only access to members, events, announcements or ministries without also being able to change them.
  • Exporting now needs its own permission instead of riding on the reports permission it never actually used. Events, Users and View-only admins keep everything else and lose export until you grant it; Reports and Finance admins keep it.
New

The public website was rebuilt

  • The home page opens on a live demo of the mobile app, with screens that advance on their own — and it holds still for anyone who has asked their device to reduce motion.
  • How it works steps through the app with the screens layered behind it, instead of sitting as one still picture.
  • Seven public pages now share one navigation and one footer, so the site stops drifting between them.
  • The pricing on the home page is read from the plans themselves, so it can no longer disagree with what checkout charges.

1.3.0

Oct 04, 2026 · 2 changes
New

Storage allowances now say exactly what each plan includes

  • Free Trial includes 10 MB, Starter 50 MB, Professional 500 MB and Enterprise 1 GB.
  • Sizes show in the unit that fits them, so a small plan reads in megabytes instead of rounding down to zero.
  • Pricing, Church Profile and checkout all show the same figure for the same plan, and Church Profile shows the amount actually enforced for your church family.
New

Collapse the sidebar and the icons still explain themselves

  • Hovering an item on the collapsed sidebar shows its name, so the rail stays useful when you want the space back.
  • Tooltips settle where they belong and fade out, instead of blinking into place.

1.2.0

Oct 02, 2026 · 3 changes
New

Event and announcement types belong to each church

  • Types are now managed per church, so one church's categories no longer appear in another's.
New

Church Profile explains what your family shares

  • The member-seats and storage figures carry an explanation of what is shared between a church and its satellites, and what is not.
  • The header logo returns you to the dashboard, and the brand reads Ekklesia PH.
New

Recurring events can be changed one occurrence at a time

  • Editing a recurring event asks whether you mean this occurrence only, or this and everything after it.
  • Volunteers are recorded per occurrence instead of for the whole series.
  • Each event shows the next date a member would attend.
  • The occurrence notice sits in the event header, and a saved occurrence edit stays on the calendar.

1.1.0

Sep 30, 2026 · 15 changes
New

A public changelog

  • This page. Everything we release, written for the people who use it, readable without an account.
  • Linked from the footer of the public site and from the admin sidebar.
New

Event reminders now reach every start time

  • Reminders fire for events starting at any minute. Previously only events starting on the hour were reached, so an event at 6:30 PM could never be reminded.
  • The reminder says how much time is actually left, and a completed event can be revived.
  • Push no longer depends on the email preference — a member with email switched off still gets the push.
New

Guest invite links work end to end

  • An invitation link now recognises its token, and accepting it makes the person a member.
  • First name and surname are captured separately, and a bad email is flagged in the form rather than after submitting.
  • The Invite action sits with the other row actions, beside Remove.
  • The waitlist email honours the member's notification preference.
New

A consistent design system across the whole admin

  • Every table, select, input, button, modal, card and image in the admin now comes from one shared component library, so a pattern looks and behaves the same wherever you meet it.
  • Colour pickers, charts and switches are shared components too, replacing one-off versions that looked nearly — but not exactly — alike.
  • The component library has its own documentation site, listing each component with its options.
New

Redesigned pages

  • Church Profile, Profile, Settings, Events, Event Details, Ministry Details, Announcements, Product Details, Asset add/edit, Invite Code, Change Password, Refund Requests, Borrow Requests, Merch Orders and Satellite Churches were each rebuilt around a consistent layout.
  • Pages that had grown extra panels and duplicated facts were reduced to one place for each fact.
New

Dark mode

  • Dark mode was corrected across the admin — accent colours are legible again on dark surfaces instead of sinking into the background.
New

Undo for deletions

  • Deleting or deactivating a record now offers an Undo in the confirmation toast, and the row comes back on screen without a reload.
  • Undo stays available while you hover the toast, so a long confirmation is not cut short.
New

A calendar view for events

  • Events can be viewed as a month calendar, with multi-day events drawn as spanning bars.
  • Hovering an event opens a quick view without leaving the calendar, and clicking a date starts a new event there.
  • Your chosen view is remembered.
New

Giving history and voiding

  • A giving record can now be voided instead of deleted, keeping the record, its receipt and its audit trail.
  • Each giving has a history panel showing who changed what and when.
  • The Givings page gained a time filter and a unique-givers summary.
New

Search and filters that keep up

  • Filter controls accept several values at once and summarise the selection instead of showing only the first.
  • Selects flip upward near the bottom of a page instead of opening off-screen.
  • Search fields no longer overlap their own icon, and no longer search the previous term while you type.
New

Reports rebuilt

  • Every report was rebuilt on the shared component library, with corrected figures: a finance total that was missing giving, event counting, organisation totals, and merch orders disappearing from totals.
  • Adds a role-over-time chart and search on the organisation reports.
New

Admin permissions are enforced

  • Admin capabilities are now checked against the API, not only used to hide buttons. A page a role cannot use renders a clear denial instead of a broken shell that fails on every action.
  • The Reports section follows the View Reports permission it actually needs.
New

Locations and venues

  • Location entry has a working map picker and server-side geocoding, so a venue is confirmed on the map rather than typed and hoped for.
  • Events carry a venue label, shown wherever the full address would have been printed.
New

Register a guest for an event

  • Admins can register someone who has no account for an event, without creating one first.
New

Discipleship

  • Discipleship requests are one live request per person, not one per pair and type.
  • Relationship-gated profiles: a member's details are visible to their discipleship counterpart, including their profile picture.
  • A taken phone number is explained, instead of reporting an unexpected problem.

Built, but not switched on yet

These are finished and will appear in the app once the reason below is resolved. We list them so nothing is a surprise later — they are not usable yet.

Not yet

Event promotion videos and recordings

Built and ready, but switched off for now: our storage cannot accept files this large yet. The feature is finished and will be turned on once storage allows — nothing needs to be rebuilt.

  • Promotion videos can be uploaded on an event, with per-card upload progress.
  • Post-event recordings can be added and edited.