Frequently asked questions

You can go either way, whenever you want. Hosted and self-hosted run the same code, so a full export from one side imports cleanly into the other — territories, publishers, documents, programmes, everything. No vendor lock-in: a real round trip, not a one-way escape hatch.

Managed hosting supports up to 200 publishers — more than enough for most congregations. Self-hosted instances have no limit at all. If your congregation needs more on managed hosting, contact us.

Yes. You can define recurring programme templates, assign speakers and service roles, detect conflicts with members' days off, and export polished PDFs. Each template can even be delegated to a specific brother.

Yes. From their profile, every member generates a private iCal link they paste into Apple Calendar, Google Calendar, Outlook, or any standard calendar app. Their speaking parts, service roles, and days off appear automatically — and update on their own as the programme changes. The link can be regenerated or revoked at any time.

You can create as many custom roles as you need. Built-in roles (Elder, Pioneer, Anointed, Brother, Sister, Ministry-school student…) come ready and update themselves automatically when you change a publisher’s profile. On top of those, build your own roles — a Service committee, Group overseers, a PR coordinator — and pick exactly which of the 20 permissions they carry.

Visiting speakers live in their own registry, separate from publisher records. Each entry has a name, originating congregation, phone, and notes. When you assign a programme part — typically the public talk — managers pick from this list instead of (or alongside) a local publisher. Speakers no longer needed can be archived and unarchived later, so the picker stays clean without losing history.

They appear in the publisher list with a Ministry-school student status and can be assigned to programme parts (student talks, reading) before they’re declared publishers. The list shows everyone the assembly has on record — publishers and students alike — so no one is invisible to programme organizers.

Every member records their own days off from their profile — start date, end date, done. When an organizer tries to assign a programme part during that range, Unitae blocks the assignment with an explanation. And if a member declares a new absence after assignments are already in place, every affected event is flagged with a warning so nothing slips through.

Both. Unitae sends transactional emails (invitations, password resets, trial expiration) and reminders for things that need action — overdue territories, monthly report deadlines, new documents posted in your sections. Members adjust which reminders they want from their notification preferences. The dashboard urgent strip carries the same information for anyone who'd rather check the app.

No, that's deliberately out of scope. Unitae tracks planned absences (every member declares their own days off) and programme assignments — enough to know who's expected. Tracking actual presence crossed a line we didn't want a member-facing tool to cross.

Yes. The publishers section shows report status for every member month by month — submitted, missing, or inactive. You see at a glance who you still need to follow up with.

Yes. Unitae generates PDF territory cards in one click, with an optional embedded map page. The S-13 report is also generated automatically from your territory data.

Yes. The interface is fully responsive. Publishers can check their territory, submit absences, or view the information board from their phone without installing anything.

Yes. Each programme template can be delegated to a specific brother. They manage their own template independently while the coordinator retains oversight.

They won’t miss anything. Unitae is designed to support existing relationships — publishers still talk to their group overseer, who can enter reports on their behalf. Elders can create and manage a publisher’s data in the app without that publisher ever needing an account. Territory cards can be printed as PDFs. The members who don’t use technology will not even notice the change — but the elders managing their information will save hours.

Absolutely. Your data is hosted in France (OVH, Gravelines), encrypted, and isolated from other congregations at the database level. Unitae is GDPR compliant by design.

All primary data is stored at OVH’s data center in Gravelines, France. No data is transferred outside the European Union without your knowledge.

No. Each congregation’s data is strictly isolated at the database level using PostgreSQL Row-Level Security. It is architecturally impossible for one congregation’s data to appear in another’s view.

Yes. Logins, data exports, anonymisations, consent changes, user creation, password operations, calendar-feed token activity, and territory edits are all recorded with the actor, the time, and the affected entity. Admins review the audit log from Settings to answer ‘who did what, when’ — useful for a circuit overseer’s visit or a data-protection question from a publisher.

Your data is always yours. You can export everything — publishers, territories, reports, programmes — at any time. And because the entire codebase is open source under AGPL-3.0, Unitae can never disappear. Even if MindsersIT stopped tomorrow, any technically comfortable member could download the code and run the exact same application on their own server. Your congregation is never locked in.

Yes. Unitae is designed for GDPR compliance from the ground up: your congregation is the data controller, MindsersIT acts as processor under a Data Processing Agreement (DPA). Built-in tools for data export, anonymization, and consent management are included.