Admin Overview
If you've just been made an administrator, this is the short version of what you can now do and where it lives.
There's no single admin dashboard
ChurchNET doesn't put administration behind one door. Each module carries its own admin controls, and you see them when you open that module with the right permission.
The three places that are genuinely church-wide:
| Screen | What it controls |
|---|---|
| Module Management | Which modules exist and how the home screen is arranged |
| Admin Permissions | Who can administer what |
| Church Info | Service times, address, contact details |
Everything else — attendance reports, event registrations, volunteer schedules — is managed inside its own module.
Two kinds of administrator
App Admin has full access to every module and every setting, and is the only role that can change other people's permissions. Keep this to leadership and office staff.
Module Admin has admin rights to specific modules only — a volunteer coordinator who manages the schedule but has no business sending congregation-wide texts.
Admin Permissions covers both in detail, and Module Permissions lists all fourteen modules you can grant individually.
A sensible first week
- Turn on only what you'll use. A new church has just Directory and Church Info enabled. Add modules as you're ready to use them, not all at once.
- Get the directory right first. Almost everything else reads from it — birthdays, the member map, event registration, messaging. Data Import can bring your existing records across, and ChurchNET will help you do it.
- Fill in Church Info. It's what visitors and new members look at first.
- Name a second App Admin. One administrator is a single point of failure — and people change phones, lose passwords, and go on holiday.
- Then invite everyone. Inviting Members.