Help center

Your day at a glance: what is waiting on you, what you have on in the next seven days, and what has been posted for you.

How things stand across the part of the organization you look after: what is waiting first, then the headline numbers, then a section for each subject. Staff and volunteers see My board, about their own work.

Conversations with people in your organization: one person, a few, or a group reached by unit and role.

Your own settings for Messages: saved replies, the conversations you muted, how messages reach you, what this device keeps, and the keys.

The messages and posts people reported to you as their safeguarding lead: why, who reported it, the words, and what has been done.

Everything sent to you, newest first: what needs you, what is new, and what has already been dealt with.

The settings that follow you, not your unit: notifications, how you sign in, where you are signed in, your clock, your details and a copy of your data.

Your documents, and the ones people have shared with you: upload them, share them, read what you are asked to, and keep their versions.

Every file people outside your organization can open: who it went to, who opened it and when, and when it ends.

What you asked to buy, and where each request stands: approved, ordered, and what has arrived.

What you spent for the organization from your own pocket, claimed back: who agreed it, and when you were paid.

Forms and surveys you are asked to answer, responses waiting for your approval, and the forms you run.

One form you run: build its questions, publish and share it, read its responses, and choose what happens when one is sent.

A form or survey you are asked to answer, and what became of what you sent.

Everything you have been asked to do, in one place: what is waiting on your answer at the top, then one list of the rest in order of when it is due.

The teams you are on: who leads each, how many are on it, and how busy its wall has been.

One team's wall: what its members say to each other, which only they can read.

Everything said in all the groups you are in, on one wall, newest first, with your groups' next meetings beside it.

Every meeting of every group you are in, in one list on one clock: this week, later, and the last four weeks.

The groups you run and the groups you are in, invitations waiting on your answer, and the requests to join you are still waiting on.

One group's wall: what its members post and ask, its next meeting, who runs it, and, for those running it, the ways people get in.

When the group meets, who is coming to the next meeting, and how many came to the ones held.

The photos, files and links shared on the group's wall, gathered in one place.

Who is in the group, and, for whoever runs it and its helpers, who is waiting to join, who was invited and who needs a word.

Work your units keep as boards and lists, such as camp preparations or a fundraising drive, each with its tasks and the people on it.

One project: its Overview, its tasks on a board or a list, its Timeline, the time logged on it, its files and automations, and its people and settings.

Rules that act on a project's tasks so people do not have to chase: telling people, giving a task out, adding the next task, or changing a field.

Every kind of work you can see, in one table: project tasks, governance actions, program jobs, follow-ups with donors and HR checklist items.

Planned hours from the tasks given to people, week by week, against each person's weekly hours.

One piece of work, whatever its kind: a project task, a governance action, a program job, a follow-up with a donor or an HR checklist item, on the same page.

One message, by email and in the app, to everybody at a unit, to some of its roles, or to the people who asked it for news, and how each one went.

One broadcast as its author and its approvers see it: where it stands, how many it reaches, its words, and the buttons to approve, refuse or cancel it.

A file from Drive sent to your contact lists: each reader gets an email with one button that opens it, with nothing to sign in to.

An announcement your organization sent you, in full: its subject, the unit it went to, when, and every word.

Your newsletters and reports that go on the 1st of each month with the newest file in a Drive folder: skip a month, change one, pause it or delete it.

Where the organization is going, as its Owner or an Admin shared it with everyone: the headline, why it matters, each goal and how far along it is, and your own part in it.

Every pay run you have a part in, the ones waiting for your approval first, and where HR starts a run for a unit's pay period.

One pay run: its lines, who prepared it and who approves it, and each step from draft to paid.

Raises past the Owner's limit, waiting for a second person's yes, and new bank accounts, waiting for a call-back before any pay run pays them.

Your organization's own income-tax bands and statutory deductions, allowances and benefits, how overtime is paid, the raise limit, and where pay posts in the book.

What is due on the HR records you keep, who starts and who leaves soon, the work waiting on you, and your own HR PIN.

Everybody you keep HR records for, a page at a time: where they sit, the footing they work on, when they started, and what needs attention first.

Everything HR keeps about one person, in tabs: employment, documents and checks, pay, emergency contacts, time and leave, history, and what joining and leaving, letters and reviews add.

Your organization's own fields about its people, such as a staff number or the languages they speak: shown on each HR record, in the People download, and read back by the people import.

Who reports to whom, drawn from Hierarchy › Positions, for a unit and everything below it where you keep HR records.

How many people a unit has today, on what footing, and who joined and left in the last 12 months, for the unit and each unit below it: counts only, never names.

What waits on you when somebody joins or leaves — a checklist task, a probation review, an exit step — and, for HR, every checklist, probation review and checklist template where it keeps records.

One person's joining or leaving checklist: its tasks grouped by whose they are, what each asks, when each is due, and who checked off what.

Somebody leaving, step by step: a notice handed in or an end proposed, a second person's decision where one is needed, clearance desk by desk, the interview, the questionnaire, the settlement, and their access ending after the last day.

One person's exit, step by step — the end and its decision, the clearance, the interview, the questionnaire, the settlement and their access — each drawn for whoever takes that step.

HR's letters from the organization's own templates — offers, contracts and changes of terms people sign in the app, and certificates you issue — with what people asked HR for, and the templates.

One letter as paper, with your own step beside it — signing it, countersigning it, or HR's draft and its sending — and its audit trail and fingerprint.

Where you raise a grievance and follow it, read a case about you, and open the cases and grievances you have a part in; HR and the Owners also open disciplinary cases here and list every one they keep.

One disciplinary case or one grievance: where it stands, who does what, its hearing, its record and its outcome, with each step drawn only for whoever takes it.

How many working days your organization gives to acknowledge a grievance and to hear it, how early the reminder goes, and which days of the week count.

The vacancies you keep or hire for, every hiring step waiting on you, and where HR asks for a new vacancy from a position.

One vacancy: its request, its job post and application form, the board of applicants, interviews and their panels, the offer, the pre-start checks and the hire, each step shown only to whoever takes it.

The review steps waiting on you, the review cycles you run, and your own reviews.

One review cycle you run as HR: set it up and open it, see each person's review by its stage, name who writes the ones with nobody, ask for peer views, and close it.

One person's review in a cycle: their self review beside the reviewer's view, the meeting and the sign-off, their word on it and any appeal, and their goals.

Your own notes of your 1:1s with the people who report to you, the actions you agreed and the next 1:1 booked, and the notes your managers shared with you.

A few anonymous questions asked again and again, every week, every two weeks or every month, to see how people are, with each round's results in groups of 5.

Where a page or an action your organization's plan does not include sends you, and where reaching one of your plan's numbers does: what you are missing, the plans and packs that have it, and who can get it.

Where a change you tried lands while your organization can be read but not changed: why it was refused, and what still works.

Where you ask ORG-APP support for help, and find the requests you have made and their answers.

One request to ORG-APP support: everything written on it, its status, and where you answer.

The reports you have been asked for, the notes you keep towards each, and the ones you have sent.

A line or two towards one report, with a number or photos, written when it happens, even with no signal.

The month's totals for your unit and the units beneath it, people, hours and leave, with what happened that month below them: the page a board reads.

One report form's number and rating answers for one asking, added up from each unit to the region and the nation, for board packs and funders.

Reports you build yourself from people, hours, leave, bookings, members, tasks or a form's responses, reading only what you can already see.

The reports people have sent in: what waits for you to read or sign off, who has not sent theirs, and where each report goes next.

The forms you ask people to fill in: who is asked, how often, who reads what comes back, and how each round stands.

One report form: its questions, who writes, reads and signs it, how the round being asked now stands, and what came back.

Every shift you have clocked this month, what it adds up to, and where to ask for a shift to be put right.

Where you clock in and out, take a break, and say what a shift was spent on as you leave.

Your leave balances, broken into their parts, and the time off you have asked for.

Your published shifts for the next four weeks at every unit, with the open shifts you can take, your swaps, and when you can work.

Your teams' volunteer rotas: the days each team serves, who is on, and the open slots you can sign up for.

Your ID card on your phone, the same as the printed one: hold it up to the kiosk at the door to clock in, and again to clock out.

Your payslips, once each pay run is paid, and the bank account your pay goes to.

One pay period's approved hours, paid leave and adjustments at a unit, locked once payroll has them, and downloaded as Excel or as CSV for a payroll provider.

Timesheets, leave and corrections waiting for you to sign off, one pay period at a time.

Clock people in and out as they arrive, by pointing this phone or tablet at their ID card.

What everybody at and below your units has worked this month, added up by unit, by category and by person, from the hours they recorded.

One person's month as somebody who reads their hours sees it: each day, what it was spent on, and the shifts and notes behind any day.

A volunteer's approved hours between two days, as a certificate to print or save as a PDF.

A unit's week of shifts: who works when, in which role and place, built as drafts and then published to the people on it.

A unit's week after the fact: the published roster against the clock and the timesheets, person by person and day by day, with the late, early and missed shifts.

Everything on in your unit, and anything announced from above it, by day, week or month: events, meetings, classes, holidays and your own leave and bookings.

One event on the calendar: when and where it is, your reply, and, for whoever runs it, who is invited and who came.

An event's poster in four shapes, A4 to print, a square post, a story and a wide banner, each as a picture to share or a PDF to print.

What your organization runs, such as a convention, a camp or a monthly gathering: where each one stands, who is on it, who came and what happens afterwards.

Every program that has finished, however long ago, each opening on its last date with its report, who came and what happened afterwards.

Everybody a program has sent on to be followed up: where each has got to, who is following them up, how long they have waited, and who has nobody.

Every program of one category that is open for booking and that you can see, wherever in the organization it is run.

One program your organization runs: what needs you next, its figures, and, in its header, Settings, Share and the door, which every one of its tabs wears.

Everybody on a program for the date in view: the people coming, the crew running it, what they told you when they booked, and the door on the day.

A program's sets of groups for the date in view: discussion groups, game teams, buses or workshop tracks, each with its leaders.

Where a program stays on the date in view, who needs a bed, and who sleeps in which room.

Between booking and the day: who is ready to go, and the documents travelers sent that are waiting for a check.

The plan for the day, minute by minute, with somebody on each line, readable by everybody the program is shown to.

The jobs to do before a program, the lines of its running order still needing somebody, and the speakers, places and things booked for it from Resources.

A program's money: what came in, what is still owed, and what was spent against its budget, with everything somebody who keeps it needs to record.

What happens to the people who came: before the day, the follow-up plan; after it, who came, how far follow-up has got, and a group or a course to send them on to.

The report on a program: written by the people asked to, read by whoever runs it, and downloaded as Word or PDF.

Booking a place on a program while you are signed in, with your own details already filled in.

What you still need to do before a program you are booked on, such as a form to sign, a document to send or a payment, and the lists you keep for somebody you booked.

Everything your unit can book: its own speakers, interpreters, drivers, equipment, vehicles, venues and stock, what every unit above it keeps, and anything a keeper offers to the whole organization.

The people and things your units keep, such as speakers, drivers, equipment, vehicles, venues and stock: what needs you, and who has them when.

Everything the programs you run have booked or asked for from Resources, grouped by program, with what each keeper said.

One person or thing a unit keeps: what it is, who keeps it, who has it when, and, for its keepers, its loans, repairs and papers.

Adding one person or thing a unit keeps, so the unit and the units beneath it can book it.

The courses offered to your units, what is required of you, and the classes running now.

Every class running a course you can see: its unit, its state, its dates and who is on it.

Every class that has finished or was canceled, across every course: its roster, who completed it, and a group to keep them together.

Your own courses, made for your phone: what is next, how far along you are in each class, what is required of you, and your certificates.

Every session of the classes you are in, in one list, on each class's clock and in your own time when you are somewhere else.

Your home for the classes you facilitate: the registers still to take, what is waiting to be marked, the people asking for a place, and each class's next session.

The posts of every class you are in, in one place: announcements pinned at the top, then the newest posts, with the class each is in.

One post of a class and its replies, where a card, a notice and an announcement's email lead.

Courses in the order a unit recommends taking them: each course, how far you have come with it, and the next class to join.

What a certificate looks like and says, published at a unit for itself or for the units beneath it.

One certificate design: its words, its look, its frame and background, and a preview of what is on screen.

One course: what it is about, what it takes to complete, what comes before it, and the classes of it you can join.

One lesson or assignment of a course's outline, drawn as a participant's page draws it, for the course's editors.

A single class of a course: the people taking it, the sessions it meets for, the work it sets, and who has finished.

One lesson or assignment of your class on a page of its own: what to read or watch, what to hand in, and when it is due.

A class's quiz as you take it: its rules, your attempts and what counts, and the paper, one question to a screen.

Who holds the courses their unit requires, who is lapsing soon or overdue, and what each unit requires of whom.

Everything posted for you, on one page: your units' notices, notices sent down from the units above yours, and your teams' and groups' walls.

Every board and committee you can see, what is waiting on you, what they have lately decided, and their meetings coming up and already held.

Every meeting you are on the list for, on a calendar: the boards you sit on, and any meeting you were invited to.

One board or committee: who serves on it, how it decides, when it meets, and its meetings, decisions, plans, papers and actions.

One board's register of interests: what its members hold that could pull against it, standing and ended, read before a matter is discussed.

One meeting of a board: its agenda and papers before, the roll, motions and votes on the day, and its minutes and actions after.

Every decision the boards you can see have taken, a meeting at a time: what each resolved, how the vote went, and whether it still stands.

Every job the boards you can see have given out that is still open: who has it, when it is due, and what is late, stuck or on nobody.

Whether your boards are working, over the last year: how often each met, whether it was quorate, whose minutes are still not approved, and how late its work is.

What the boards you can see have committed to do, the plans in most trouble first, with how far along each goal is and what waits on a board.

One strategic plan in full: where it is in the board's process, each goal against its pace, the readings and work beneath them, and what the board has decided.

One goal of a strategic plan: its target, owner and period, its readings, the projects put toward it, and the board's actions toward it.

Every email your organization has sent or tried to send, what became of each one, and the addresses mail no longer reaches.

Every setting you keep, on one menu: grouped as Settings groups them, each with a line on what it is for. On a phone it is the way into each of them; on a computer the menu is beside it, and Settings on the left opens a setting itself.

The kinds of event on your calendar, in your own words: they fill the Category box on the calendar's event form and the calendar's filter chips.

The kinds of program your organization runs: every program is filed under one of these, and only these.

What a department is for, in your own words: these color the departments on the structure, and are what a ready-made structure files its departments under.

What happens to people after a program: each track is a named list of stages, and people move along it one stage at a time.

Whether your organization runs informal groups that cross units, and whether people from outside it may join them.

One line on everybody's home page each morning, chosen from your own library of lines, or none at all.

Every rule on the projects you can open, in one place: rules that act on a project's tasks so people do not have to chase, with how often they have run and what they did.

Bring work in from another tool: an Asana project, a Trello or monday.com board, or any spreadsheet becomes a project at one of your units, and a class you run can be brought in from Google Classroom or a spreadsheet.

What each role lets somebody do: the built-in roles every organization has, and the roles your organization makes for itself.

The designs your events' posters are drawn from: made once at a unit, for itself or every unit beneath it, so a poster for any event is then a minute's work.

How recorded time is counted, one unit at a time: rounding, overtime, how long a shift may stay open, and what a shift must say.

What working time is spent on, in your own words: they fill the Category box when somebody says what a shift was spent on, and break down the hours in time reports.

How a timesheet travels here, and who decides each step: worked, confirmed by its person, approved, signed a second time where you ask, and payroll.

Fixed shifts or flexible hours, unit by unit and person by person, and when late, early and missed shifts are passed on to a lead or the Coordinator.

The kinds of leave people can ask for, which are the same everywhere, and how much each unit's people earn of them, which a unit sets for itself and the units beneath it.

How every ID card looks, and the kiosks at your doors: a card is scanned at a kiosk, or by a lead's phone, to clock in and out.

What the whole organization starts from: its name, clock, currency and language, how people sign in, its logo and app, and its web address.

What people see at your organization's address before they sign in: a home page, more pages where your plan has them, pages for units, and your programs on a website of your own.

One page of your website beside its home page: its words, its address and cover picture, and whether it is published and in the menu.

Sign-in, the app and your website at an address of your own, such as app.northfield.org, instead of your address on ORG-APP.

How ORG-APP confirms who runs your organization, so that it can take money and carry the Verified mark.

Your own words for the layers of your organization — nation, region, chapter, assembly.

What your organization uses, within what its plan includes: switch off what you have no use for, and it comes back as it was when you switch it on.

Whether your people may sign in with a passkey — their fingerprint, face or device PIN instead of a password — and whether your administrators must have one.

Your people sign in with your own identity provider — Microsoft Entra ID, Google Workspace, Okta or another — at the email domains you prove are yours, and your directory keeps their accounts and seats.

Keys that let your other systems — a payroll provider, a spreadsheet, a website — read and change your records, and addresses where ORG-APP sends your own systems a message when something happens.

Connect your own Claude, ChatGPT or Microsoft Copilot to ORG-APP so it can ask as you, choose what it may do, see every question it asked, and end it.

The page an assistant you are connecting opens, where you read what it asks to do as you and allow it or say no.

What the assistant in the top bar may spend each month, whether what people ask it is kept, and what it has cost so far.

How people who book your programs and give to your funds pay: each unit's named payment routes, the ones it uses by default, and the changes waiting for an owner's or admin's approval.

Your organization's plan and paying for it: the trial, the next invoice, packs and add-ons, text credit, this month's video minutes, and the card kept with Stripe.

The steps an expense claim — or, where Purchase orders are switched on, a purchase order — goes through, in order, before whoever approves money at its unit agrees it.

Your organization's credit for codes, reminders and broadcasts by SMS and WhatsApp: what is left, what it went on, and where codes may be sent.

Taking a copy of all your organization's records out, choosing where its documents are kept, linking its privacy notice, and what ORG-APP keeps and for how long.

What was done in your organization, by whom, when and where: its own audit log, with filters and a download.

Your organization's rules for files that leave it: who may share them outside, how long links last, the folders that never leave, what readers can do, and the emails your contacts get.

How each group of notices reaches people by default, by phone and by email, and the Slack and Microsoft Teams channels that hear about what happens.

Everyone seated in the units you can see and what they do there, and where you find, add, invite and download them.

One person's seats, what each lets them do and asks them to submit, and their record, as far as you may see it.

Who at a unit has an ID card, issuing cards to the rest, printing them, and replacing a lost one.

Put a list of people on the books from a spreadsheet, each with a seat at a unit, checked in full before anything is written.

Everybody who took part in one of your programs or courses, with an account or not: one record each, and everything they took part in.

People outside your organization who hear from you and never sign in: the lists you put them on, and how each agreed to hear from you.

The memberships of the units where you run membership or keep its dues: who is a member, of which kind, who has applied, and who is due to renew.

One membership: who it names, where it stands, its dues and how each was paid, and its member card.

How your organization is shaped — countries, regions, chapters, or whatever you call them — and how many people are seated in each unit.

Build or add to your hierarchy from a spreadsheet, one row a unit, checked in full before anything is made.

Lay down a common shape for your organization in one go: its levels, units, departments and teams, ready to rename.

What each unit does: its departments, the teams inside them, and who leads and works on each.

Where several people share a role at one unit, a named position for each, so each reviews only the people who report to it.

The units whose page on your organization's website you write, and whether each has none yet, a draft, or a published page.

Write one unit's page on your organization's website: what it says, when and where it meets, whom to contact, its pictures, and whether it is published.

What a new organization still needs, worked out from what is really here, with the way to each step.

How one unit's money stands — its cash, the month's money in and out, the budget — with everything waiting on you, and what the programs and classes whose money you keep are owed.

Every gift to the units whose book you read, as it went into the book: who gave, how much, for what, its receipt, and whether they have been thanked.

The people and organizations who give to the units whose book you read, who looks after each, and how each likes to be reached.

One donor: who they are, how they like to be contacted, every gift and every contact beside it, the next contact planned, and what they have pledged.

What donors have promised — so much, so often — how much of it has come, and who is behind.

How one unit thanks its donors: the gifts still waiting, how quickly they are thanked, its own wording, its receipts, its Give page, its funds and the year-end statements.

What units owe the units above them, what has been paid and what is late, seen from both ends, so the two books agree.

The rules the units below a unit owe it by and, for a period, what each would owe, worked out before anybody is billed.

A unit's bank, mobile money and cash accounts beside what their banks say: where each one stands, and the statements uploaded.

One account's statement lines, each matched to what the book already has or put in an account, so its months can be reconciled.

Each month of an account, in order, checked against the bank's closing balance, or a cash box counted at the month's end.

What people spent for the organization, as the finance desk sees it: who claimed it, who agreed it, and whether they have been paid back.

What the units owe their suppliers and when it is due, with each bill paid, undone or voided here.

Spending agreed before it is committed: asked for, approved by amount, ordered from the supplier, received, then matched to the supplier's bill.

Who the units buy from and pay: how to reach them, how to pay them and who last changed that, and what is owed to each now.

What a unit plans to spend and raise, month by month, beside what the book says it actually has.

Every entry in one unit's book, over any dates: found by its words, an account, a fund, an amount, a program or where it came from, and posted, copied, reversed or downloaded by whoever keeps the book.

The accounts every unit's book uses, one chart for the whole organization, with the chosen unit's balances beside them.

Money given for a purpose, and what is left of it in the chosen unit's book: each fund's balance this year, and the funds themselves.

One unit's year, month by month: each month's sign-off, the balances its book opened with, when its year starts, and closing a year.

The chosen unit's book posted to Xero or QuickBooks Online, once an entry, through the accounts you map: where it posts, what went, and what waits.

The Reports tab: the statement of activities, a unit's income and spending over any dates, and the list where you choose any other report.

Any report but the statement of activities, for one unit's book: the financial position, cash flow, fund balances, the general ledger, the trial balance, spending by purpose and the giving reports, each with its own title in the header.

Every unit whose book you read, side by side for one month: who has closed it, and what those who published reported, each currency on its own.

What customers owe each unit: every invoice sent, seen, paid or late, how late the money owed is, and each invoice with its payments, credit notes and what it posted to the book.

Who each unit sells to and invoices: what each owes, how much of it is late, how quickly they pay, and each one's invoices, payments and statement.

What each unit sells and for how much, with the income it earns and its tax: picked on an invoice's line instead of typed.

How a unit invoices: its numbers and terms, its reminders, the address and words on every invoice, where customers' replies go, the accounts its invoices post to, and its tax rates; and, where the Sales pipeline is on, the stages every unit's pipeline moves its deals through.

Work you hope to win, from first talk to a signed yes: every deal on a board of stages, what it is worth and likely to bring in, and its invoice made the day it is won.