How to use kaycie

1. Go to /login and sign in with your email and password. Your invite email has a set-password link.
2. You land on Home: what is waiting on you, your figures and a few quick actions. Each waiting item has a button that opens where you clear it.
3. The side menu lists only the areas you have access to, grouped the way the work flows. Needs attention shows a count of what is waiting on you. On a phone, press Menu at the top.
4. The bell at the top opens your notifications, at the foot of Home. The slim banner at the top of a dashboard shows how many things need you, and goes when you’re caught up.

Why: kaycie shows each person only what their access allows. That is the safeguarding and compliance model working. If a page says you don’t have access and you need it, ask your admin to add it on the Team panel.

1. Big lists have a search box on top. Every word you type must match, and a number finds that exact record. A long list says Showing N of TOTAL, with a show-more link.
2. Click any column heading to sort the table. Where a form asks you to pick a record, it’s a dropdown, with a type-to-search box when the list is long.
3. In the side menu, press a group’s name to fold it away; kaycie remembers. A greyed item with a package name beside it (Plus, Complete) isn’t in your package yet: press it to see what it does.
4. Closed sections are small blocks, side by side; open one and it takes the full width. Whenever you press Open (on Needs attention, a notification, a link), kaycie opens the section it points to, scrolls to it and lights it briefly.
5. At the foot of most dashboards, Runs on lists the settings that page depends on (PayFast, VAT, your mode), each linked to where you change it.

1. On a phone, lists become cards showing the essentials.
2. Tap a card to unfold every field (dates, status, the lot). Tap again to fold it. Links, buttons and the ⋯ menu work as normal.

1. Every table has Export (CSV). Where you add records by hand (contacts, organisations, students, programmes, enrolments, budget lines, wishlist items, regular payments, manual entries, reminders) it also has Import (CSV).
2. Export first and you have the exact layout. Edit it and import it back: a filled id updates that record, a blank id adds a new one.
3. Check file checks without changing anything. If any row is wrong, the whole file is rejected and nothing changes.
4. Payments, donations, quotes, invoices, consent, resolutions, minutes, documents and the media library are export only.

Why: those come in through their own screens, so their checks (reconciliation, sign-off, signatures, consent evidence) always run.

1. Press Watch on this page and the walkthrough plays in a window, on your own pages, by itself. Pause it any time, or press Try it yourself to do it for real.
2. On a dashboard, Show me how to buttons highlight each part of the page and explain it; you do your own work as you go. One that starts on another page plays in the window.
3. Where a walkthrough fills in a form, it types sample answers and shows the success message. Nothing is ever saved: the save is stopped and the form clears when it ends.
4. Press Next to move on, Back to read a step again, or Escape to stop.

1. Waiting on you: decisions and signatures only someone with your role can give. Quotes to sign off, resolutions to vote on, a donation to reconcile before its 18A, photos waiting for review. The banner on every dashboard counts only this section.
2. Still open: everything outstanding that isn’t waiting on a decision. EFTs not yet matched, 18As requested but not issued, promised donations not received, students without consent on file. It has a CSV export, and a monthly email goes to the oversight team.
3. Each line opens exactly where you clear it. Every decision lands in the audit trail, and unless your Approval rules allow it, nobody signs their own submission.
4. To chase people, Remind everyone who can decide nudges everyone who can act on that section’s lines, in-app and by email, once per line per day. Each line has the same button for one nudge.

Why: a one-person organisation usually finds Waiting on you empty, and Still open is its to-do list. That’s expected.

1. Progress updates, consent renewals and statutory deadlines show under Reminders & deadlines two weeks before they are due.
2. Assign gives one to a team member. Only people who can do that work are offered, and they are told. If only one person can do it, it’s theirs automatically.
3. Done ticks it off. Saving a student’s progress report ticks off their update by itself.
4. Reminders nobody has been given yet are counted under Waiting on you.

1. By email: connect your mailboxes, such as info@ or donations@. Each new email becomes a conversation within about five minutes, and when they reply to your answer it joins the same conversation.
2. From your website: the kaycie message form on your own website sends each message straight to the Inbox. If your website already has a form that emails you, those emails arrive through your connected mailbox.
3. By WhatsApp: messages to your organisation’s WhatsApp number, once it is connected.
4. kaycie matches the sender to a contact by email. Someone it doesn’t know shows as New contact?: open the conversation and link them to a contact you have, or add them. Nobody is added on their own.

Inbox is part of the Complete package.

1. Open Admin & setup, the Conversations card, then Mailboxes.
2. Choose where the mailbox is: your web host (most South African hosts), or Google. Type the address and its password. Google needs an app password, which needs 2-Step Verification switched on.
3. Choose who new emails to this mailbox go to, or leave it to your rules and default person. Press Connect mailbox: kaycie signs in to check before it saves anything.

Why: kaycie only reads. Nothing in your mailbox is marked read, moved or deleted, and older emails stay where they are. Replies go out from the same mailbox, so people see your own address. Newsletters and automatic replies are left out. Microsoft 365 mailboxes can’t be connected yet.

1. Open Admin & setup, the Conversations card, then Website form. Check your website address is listed: the form only shows there.
2. Copy one of the two lines of code: the form in the page, or a Message us button in the corner.
3. Paste it into your website: in WordPress a Custom HTML block, in Squarespace a Code block, in Wix Embed code. Whoever looks after your website can do this in a few minutes.
4. See it on a sample page shows how it looks before you add it.

Why: people write to you without leaving your website. The form uses your brand colours, names your organisation and links to your privacy notice. Each message lands in the Inbox with the topic they chose, so your rules send it to the right person.

1. Open Inbox. Filter by status, who has it, subject, tag or channel; Mine shows yours.
2. Open one to read the thread. Reply sends an email from your organisation’s name; choose what happens next: waiting on them, keep open, or resolved.
3. Add a note for your team. Notes are never sent.
4. On the right, set who has it, the status, subject, tags and the day it should be answered by.

1. Open Admin & setup and the Conversations card.
2. Add rules like “if the subject is 18A certificate, give it to someone with the Donations & Sales job” (they also need the Inbox tick) or “if the first message mentions refund, give it to Ana”. Rules are checked from the top; move them up or down from the ⋯ menu.
3. Choose a default person for anything no rule fits, and how many hours a message has before it is past its due-by.
4. Edit your own subjects and tags there too, one per line.

1. Conversations nobody has, and ones past their due-by, show on Needs attention.
2. Whoever has overdue ones hears about it each morning.
3. On your profile, choose how you hear when a conversation is given to you: email now, WhatsApp once your organisation connects it.

Why: alerts give the subject and a link, never the message. The audit trail records who did what with a conversation, not what was said. If a person asks to be erased, their conversations are blanked too.

1. You plan your posts on one calendar, so the team can see what goes out and when, and nothing is posted twice or forgotten.
2. Every post is approved before anyone shares it, and only photos with consent can be used, so what goes out is right and safe.
3. Your team shares from their own accounts. One message reaching their friends and family travels further than a post on your page alone.
4. Email journeys then follow up for you: the welcome, the thank-you, the nudge to a lapsed donor, each at the right moment, without anyone remembering to send it.
5. Stories and free guides give people a reason to come back and to join your list, with their yes on record.

Why: Most people need to hear from you several times before they give, volunteer or share. kaycie makes those moments happen on time, from one place, with consent built in.

Marketing is part of the Complete package.

1. In Marketing, press + Add a post, or double-click a day on the calendar. Write the caption, choose the networks and a date, and pick a photo with consent or a published story.
2. Press Approve. kaycie checks the photo is still cleared before the share buttons go live.
3. Press WhatsApp, or open the ⋯ menu: each network button copies the caption and opens that network, ready to paste.
4. Press Mark as shared in the ⋯ menu. To reuse a good post, press Duplicate.

Why: a post approved by one person and shared by many reaches far more people than one post on your page, and the calendar shows everyone what is coming.

1. Each team member switches on Nudge me on WhatsApp on their own profile. It is off until they do.
2. At a post’s scheduled time, kaycie sends them one WhatsApp message with a link to the post’s share page.
3. They open the link, save the image, copy the caption and post it from their own account.

Why: people trust a post from someone they know more than a post from an organisation.

This uses the WhatsApp number connected in Inbox and one approved message template.

1. On the Social posts card, press Saved locations.
2. Open your place on Instagram, copy the address from the browser, paste it in, and give it a name. Press + Add a location for another.
3. When you add a post, choose it under Tag our location.

Why: a tagged place helps people nearby find you, and shows your work is real and local.

1. On the Social posts card, press Links page and add the buttons you want: volunteer, an event, your newsletter, a free guide.
2. Press See my links page to check it. Your Give button is always first, and your latest story is under the links.
3. Put that one address in your Instagram, TikTok and Facebook profiles.

Why: social profiles allow one link. This makes it count: giving first, then everything else.

1. Set up your own sending address on Setup. It must be on your organisation’s own domain, such as info@yourcharity.org.za.
2. In Marketing, find Email journeys and switch on the ones you want. Off journeys stay greyed out.
3. Press Open to read every email as people will receive it, and Send me a test.
4. Press Edit to change any word, the style or the photos. Restore the standard copy undoes your changes.

Why: each journey is written for one moment: a new supporter, a first gift, a monthly donor, a new volunteer, an 18A certificate, a lapsed donor, a free guide. Sent on time, the right words turn a first contact into a relationship.

Every email has an unsubscribe link, and journeys that need consent only reach people who said yes.

1. Welcome a new supporter: people decide how they feel about you in the first two weeks. Three short emails introduce you while they are listening.
2. Thank a first-time donor and Welcome a monthly donor: a real thank-you and a picture of what the gift does make a second gift far more likely.
3. Welcome a new volunteer: clear expectations and a warm welcome mean more volunteers turn up and stay.
4. After an 18A certificate and Reconnect with a lapsed donor: a well-timed note brings back people who simply were not asked again.
5. Deliver a free guide: sends the guide someone asked for, then one gentle follow-up.

Why: these are the moments where charities most often lose people, simply because nobody followed up in time.

1. Switch the journey on, then press Add people on its row.
2. Press Add everyone who qualifies, or tick the people you want. Only the right people are offered, for example volunteers for the volunteer journey.
3. Press People any time to see who is in a journey, which email they get next, and to remove someone.
4. To add one person, open their contact record and use Email journeys.

Why: your existing volunteers and donors deserve the same welcome and thanks as new ones. Their first emails go out a minute or two apart, so a big group arrives gently.

1. Every email has an unsubscribe link, plus the one-click unsubscribe button Gmail and Outlook show.
2. Once they unsubscribe, they get no more journey emails or newsletters, and cannot be added to a journey.
3. Their contact record shows the date. Use They asked to be added back only if they ask you.

Why: respecting a no keeps your emails out of spam folders and keeps you on the right side of POPIA.

1. In Marketing, find Stories and press + Write a story.
2. Give it a title, tell the story, add a short summary and a cover photo with consent.
3. Press Publish to put it on your stories page, or Save as draft to finish later. Drafts stay private.
4. Press See our stories to read it as visitors do, and Make a post from this in the ⋯ menu to share it.

Why: stories are your blog. They show what a gift does in a way numbers cannot, and give every post and email something real to link to. Use first names only, and only with consent.

1. In Email journeys, press Guides on the Deliver a free guide row.
2. Under Make a guide from your stories, give it a title and a short note, tick the stories, and pick a cover photo.
3. Press Make the guide. kaycie builds a designed PDF in your colours. Press PDF to check it.
4. Press Copy link and share the guide’s page. People give their name and email, download it straight away, and can tick to hear from you.
5. Switch on Deliver a free guide so those who tick get it by email with a follow-up.

Why: a free guide gives people a reason to join your list, with their yes on record. You can also upload a guide you already have.

Making guides from stories needs the Certificates add-on switched on. Press Rebuild after you change a story.

1. On the Stories card, press Page style and Give button.
2. Choose Organic, Classic or Photo. Press Preview to see each one.
3. Set where the Give button goes: your donation page, a PayFast or BackaBuddy link, or a campaign page.

Why: your stories page, links page and guides then look like one family, in your two brand colours.

1. Open Contacts and Add a contact, or let people add themselves through the Get involved form on your website.
2. Fill in the name and email. kaycie de-duplicates by email, so the same person never becomes two records.
3. Tick the consent box only if they agreed. The wording is first-person on purpose, because it records what they agreed to, and kaycie stamps the date as your POPIA proof.
4. Tick Donor or Volunteer to say what someone is. kaycie ticks Donor for you the moment a donation is promised or a payment is recorded. Team access isn’t here: that’s the Team panel, because it opens doors.

Why: one record per person. Duplicates split someone’s donation history and break their 18A paper trail, so capture an email when you can.

1. Export with the Export buttons: All contacts for admin, Opt-ins only for anything marketing.
2. Bringing a list in? Open Import contacts and press Download a blank template: the exact columns, required ones marked, and one example row to overwrite. (With records already on file, Export gives the same layout with your data.)
3. Press Check file first to check without importing. If the columns don’t match or a row is invalid, the whole file is rejected with the reason.
4. People already on file are matched by email and updated; new emails are added.

1. Click a name in any list and it opens for editing, the same place the ⋯ menu’s Edit goes. The menu has everything else.
2. Names are links only where you may edit that record; otherwise they’re plain text.
3. While a form is open the rest of the page dims. Nothing is locked: hover or tab into anything to bring it back.
4. Changes save straight away and land in the audit trail.

1. If someone on file sends the Get involved form again with a new phone or email, kaycie uses the new details and logs the old value. There’s no approval queue.
2. See every change under Detail changes (audit) on Contacts: when, who, which field, and from what to what.
3. If a change was wrong (an email that started bouncing, say), the old value is right there, so you can put it back by editing the contact.

1. For donors who pay by EFT, or supporters showing interest before they give: open Link a donor (on Programmes or Donations) and pick the person and the programme.
2. Add what they intend to give if you know it. It’s optional.
3. The programme shows on their donor portal straight away. No money is recorded.
4. When their EFT arrives, record it under Donations and it reconciles against this promised donation.

1. Press Add a programme, or Edit on its row: name, type, B-BBEE category and a funding goal. Only the name is required.
2. Archive retires a programme: pickers stop offering it, and its money history stays reportable.
3. The Programme report (View on its row) shows donations in, paid places in, spend out, net, seats and goal progress, on the same conventions as Transactions.

Why: everything hangs off a programme. Wishlists raise money for programmes, Sales sells programme places and reports report on programmes, so those areas stay locked until your first programme exists.

1. Open the programme’s edit screen (⋯ → Edit on its row): Paid places is the fold below the form. The Paid places tool on Programmes opens the same form for any programme.
2. Tick delivered in individual places and set the total seats, the seats kept free for students, the place fee (once-off or monthly), and what happens to a seat when an enrolment completes or is withdrawn (the default on Setup, or your own).
3. The fee is VAT-inclusive: what you type is what the payer pays. If you’re VAT-registered, the tax invoice works out the VAT; tick VAT-exempt for exempt programmes (educational services, say).
4. Unticking paid places removes the seat settings without touching enrolments.

Why: use paid places when people take up a specific place: a course with set seats, a bursary with fixed slots. Leave it off for programmes that serve everyone who comes.

1. kaycie refuses enrolments beyond capacity, and protects the seats kept free for students from being sold.
2. Paid places never crowd out funded ones, and (per your seat settings) an ended enrolment frees its seat.

Why: “programme is full” is protection doing its job, not an error.

1. On Programmes, open Enrol a student and pick the student and the programme.
2. The enrolment is active straight away. Funders fund the programme, not individual children.
3. Progress-update reminders are scheduled on the programme’s cadence and show on Needs attention → Reminders & deadlines two weeks before they’re due. Saving the student’s progress report ticks the reminder off.

1. On Sales, open Bill a paid seat: pick the programme, enter the student’s name and email, and choose who pays (an organisation or a contact).
2. The seat is reserved and the payer is emailed the bill, with your bank details and, once PayFast is set up, a pay-online button.
3. Payers are reminded three days before the due date, on the day, and a week after, until the bill is paid. Turn this off above the outstanding invoices if you’d rather remind by hand.
4. Paid in part? The bill stays open showing what’s owed; the pay link and reminders ask for the balance, and it closes itself when the total is in. Each payment gets a tax invoice (or counts against the bill’s own, on invoice basis).
5. The bill’s ⋯ menu has Reconcile payment, Remind the payer, Pay-online link and Cancel bill. A bill with money paid on it can’t be cancelled; refund the payments first.

1. Open Programme statements: raised against spent per programme, straight from Donations and Spending, on your accounting basis.
2. Donors see the same figures on their portal, live.
3. General-fund gifts join a programme when you allocate them on Donations.

1. Students are added only by staff, on Students. Never through a public form: that’s deliberate safeguarding.
2. Set the date of birth. The minor flag works from it, and consent depends on it.
3. Link the guardian (their Contacts record) with the pencil. The guardian portal and consent requests hang off that link.
4. The Students – sensitive details tick (Team) guards the sensitive parts: the students export, consent documents and full names on media. Without it, staff work from the protected view.

Why: a parent or guardian who is your contact lives in Contacts; the protected student record lives here. Keep them linked, not merged.

1. Guardians get their portal automatically when linked to a student, and see only their own children.
2. Or grant it by hand under Give a guardian portal access.
3. Their welcome email also carries a one-time link for each consent not yet on file for their children, so one email does both.

1. Consent is recorded per area: photo & story, medical, transport, and programme participation. It can come from the guardian or the person themselves: your judgement, chosen on the form. kaycie records the basis you chose and the exact wording agreed to, and holds nothing up.
2. Media and participation can be given online. Medical and transport need a signed paper form, uploaded as evidence on Record consent, unless your organisation switches paper-only off under Approval rules on its own legal advice. Guardians can then give those online too, each with its own wording.
3. Request consent in one click: the ⋯ menu on a student’s row emails their guardian a signed link. No password, no account: they read the wording, tick and type their name. Choose the consent when you send the request.
4. It lands on your register straight away and your team is told. Guardians with portal access can also consent there.
5. The consent register shows on file against outstanding per child and exports to CSV. Any consent downloads as a PDF certificate for a school, hospital or funder, and signed forms file in the Consent documents archive.

Why: a hospital or insurer usually wants a wet signature for medical and transport.

1. Open Bulk upload consent forms and say what the batch covers. One consent type per batch.
2. Pick all the files at once. Name each after the person (Bongi Demo.pdf) and kaycie matches them for you.
3. Confirm every pairing on the review table before anything saves; assign or skip the rest by hand. Unmatched files are skipped and listed, never guessed.
4. Each saved form files on the consent record and in the documents archive, just as if recorded one at a time.

1. Build your report templates once: the fields your team fills in (text, numbers, choices, dates, even a photo). Tag each template to the programmes it applies to.
2. Report on one student from Progress report on their row, or a whole programme on one screen with Complete progress reports in bulk.
3. Photos are stored privately: staff and story reports only, never portals or public pages. Mark a field with | story to allow it into story reports; everything else stays internal.
4. Mark a field with | agg to sum it up across a group, or choose how: | agg:avg, | agg:sum, | agg:count, | agg:pct.
5. Two field types are made for it: yesno (counted, and as a percentage) and scale (1 to 5: an average, and the share at 4 or 5). Example: Attends regularly | yesno | agg.

1. On Students, open Story report: pick the template, optionally a programme and dates, add an intro, and generate.
2. The story is figures and narrative: the | agg fields as starting against current, dated, with your intro as the narrative. No personal information about any child appears. Cleared photos from the media library that belong to the programme follow the figures.
3. Only children with a current photo & story consent are included, checked when you generate. Aliases are used throughout, and the document ends with its own consent register (who consented, when, how).
4. Below the small-group threshold (five by default, set on Admin & setup) the figures aren’t shown at all, judged on the whole document.
5. Tick Attach the participants’ own story reports only when a funder asks: they go in whole, as an addendum, aliases throughout.

Who was left out? The document names nobody. Refresh Students afterwards: for half an hour they’re listed for you (full names if you can see full details, aliases otherwise), each with a Request consent link.

1. Upload a batch (JPEG, PNG or WebP). The date each was taken is read from the file; nothing else is asked yet.
2. Tick photos and say who is in them: students from the list, adults from your contacts (tick that they agreed), or everyone enrolled in a programme to pick people quickly. Your last set is pre-selected for the next batch.
3. A photo clears only when every person tagged in it is cleared: students by a live photo & story consent, adults because they agreed.
4. No one in it? Save a reason instead: no people; premises we own or control (needs the property consent record on Setup); or written consent held offline, with the file attached.
5. Add to programmes is a separate step, for grouping and the story report. It never changes whether a photo is cleared. Programme is one filter among three, beside state and student.

Why: every photo starts in Do not use and is cleared only by consent or a recorded reason, never by a manual tick.

1. kaycie decides each photo’s state from the consent register, and checks again every day and the moment a consent is recorded or withdrawn.
2. A withdrawn or lapsed consent returns every affected photo to Do not use on its own, including photos already used. That’s why the audit trail keeps the circulation log.
3. On Students, Images this student appears in shows each student’s count of cleared and do-not-use photos beside their consent state.

1. Tick cleared photos and Export cleared as ZIP for your media team. A read-me inside says what was true on that date. Only cleared photos leave, whatever was ticked.
2. The story report adds the cleared photos tagged with its programme, checked again at that moment, and records the use.
3. Every download is in the audit trail.

Why: no facial recognition, ever (POPIA s26/s34), and no photo of a child goes near a third-party service.

1. On Wishlist, create a wishlist and add items: claim (one donor covers it), co-fund (many chip in) or in-kind (goods, no payment).
2. Listing near-identical items? Duplicate on an item’s ⋯ menu copies its details, never its money; the copy starts open and unfunded.
3. Publish, then share the public wishlist page. Supporters claim items there; cash claims pay by card (PayFast) or EFT.
4. In-kind donors leave contact permission, so you can arrange to receive the goods.

Why: wishlist cash is a donation, 18A-eligible like any other gift.

1. A promise doesn’t hold an item; money does. When someone promises to pay by card or EFT, the item stays open (noted as promised) until their payment is recorded. Then it’s covered.
2. If two people pay for the same item, the second gift is still a real donation. kaycie tells you, so you can put it to the next need or thank the donor.
3. Got an item some other way? Record an outside gift marks it covered without inventing a donation.
4. Watch items flip to Covered ♥ and pull the commitments report (with CSV) any time.

1. An in-kind promise keeps the item open until the goods arrive. Then open the wishlist’s report, find the promise and press Mark received.
2. Enter what the goods are worth. The gift goes into the in-kind register on Donations (so the donor can ask for an 18A; keep a note of how you valued it), and the item is covered.
3. Money promised outside card or EFT checkout (cash at an event, say) has Mark received too: enter the amount and how it came. It’s recorded on Donations and the item is covered.
4. A promise that isn’t coming? Cancel promise on the same row. Only promises can be cancelled; anything received stays on record.

1. On the public wishlist, anything that no longer needs donations (covered, gifted whole, or a monthly item fully sponsored) moves to a greyed Already taken care of section at the bottom, labelled with why it closed.
2. It stops asking, and visitors still see what generosity has already done.
3. Reopen brings a covered item back any time.

1. Press Bulk edit at the top right of the items table. The table becomes editable: name, category, priority, quantity, cost and funding mode.
2. Change what you like, then press Review changes. Nothing is saved yet: kaycie lists every change it’s about to make (which item, which field, from what, to what).
3. Only then press Save. Rows you didn’t touch are never written, and each change goes into the audit trail against its own item.
4. If someone else changed an item while your grid was open, that row is skipped and named, rather than your edit quietly overwriting theirs.

Why: funding and status can’t be edited here. They record what actually happened to an item (donor money, outside gifts, covered or not) and change through events, not typing.

1. A supporter uses your Donate form and pays by card through PayFast, or chooses EFT and sees your bank details with a unique payment reference (set your details on Setup → Bank details (EFT) first).
2. The row shows How they chose to give: Card (PayFast), EFT / bank or In kind. Promised means no money has arrived yet; it changes to Received (or Monthly, active) the moment money lands.
3. When PayFast confirms, the payment appears on Donations by itself (amount, fees and reference included), and your Money alerts people get an email saying how much arrived and that it’s verified.
4. The thank-you page links to the donor portal and, once your 18A approval is confirmed, explains how to Request 18A there. After a money gift it also invites them to give monthly.

1. Card (PayFast): the gift is verified the moment it’s paid. Nothing to reconcile.
2. PayFast later pays the money out to your bank, minus their fee (and only after you withdraw it, if your account works that way). That deposit is the same gift arriving: never capture it again as a new EFT. The alert email says so too.
3. EFT: when a donor chooses EFT, your Money alerts people get a deposit expected email with the exact reference (PLEDGE-…) to watch for.
4. When it shows on the statement, record it under Record an EFT payment and reconcile it, or import the statement.

1. A promise reads Promised until money is recorded against it, then Received.
2. Not coming? Press Not coming on its row. It leaves the promised total and stays on file.
3. Unpaid promises close themselves: after 30 days for card and 60 days for EFT they read Promised, not received and leave the count. If the money comes later, it’s still matched.
4. A gift typed in without its promise is linked each day when the donor has exactly one open promise of that amount. Anything less certain is left to you.

1. Download your transactions as CSV or OFX from online banking. FNB, Absa, Nedbank and Standard Bank all offer it (FNB and Absa keep about three months, so import monthly). Only PDFs, like Capitec? Export the transactions from your accounting package (Sage, Xero) instead.
2. On Donations, open Import a bank statement and choose the file (FNB’s zipped OFX works as it is). Import as often as you like: lines already read are skipped.
3. Match means a PLEDGE- or ENR- reference: certain. Record the certain matches does them all at once.
4. Check means confirm it first: an EFT typed in but not reconciled, a promise or bill of the same amount, or a payment already recorded (the line just closes; nothing is counted twice). A PayFast payout is set aside: its card gifts are already recorded.
5. Anything else: New donation (general fund) or Not a gift (interest, your own transfers).

A payment recorded from the statement is reconciled at the same time. Deposits still to match show on Needs attention.

1. When a donation lands in the bank, record it under Record an EFT payment against the donor, if it isn’t on Donations yet.
2. When the money shows on your bank statement, open the ⋯ menu on the payment’s row and choose Reconcile to bank statement.
3. Enter the statement reference and the date the money reached the bank.

Why: that reference confirms you saw the money on the statement, and it goes on the permanent record with your name. Card payments don’t need this. An EFT gift can’t get an 18A certificate until it’s reconciled.

1. On Donations, find the payment. Its row shows Request 18A (anyone) and, for signatories, Issue 18A. Donors can press Request on their own portal too.
2. After the 14-day refund window, press Issue 18A. The certificate gets its unique number, is emailed to the donor as a PDF and is filed in Documents.
3. If something isn’t ready (SARS approval not confirmed, the window not passed, an EFT not reconciled), kaycie says what and doesn’t issue.

Why: twice a year, download the IT3(d) file from Reporting: by 31 October for 1 March to 31 August, and by 31 May for the full tax year.

A donation gets an 18A, never VAT. A paid place gets a VAT invoice, never an 18A. kaycie refuses the wrong one.

1. A certificate can exist only once per donation (a SARS rule kaycie enforces), so a wrong one is never edited: it’s revoked and replaced.
2. First fix the donor’s details, on their record or by having them send the 18A request form again. The replacement prints what’s on file at that moment.
3. Then press Revoke & re-issue 18A on the payment’s row (SARS Representative only). The old number is kept on file stamped VOID and drops off the IT3(d); a corrected certificate with a new number is emailed to the donor.
4. Need to check with the donor first? Revoke 18A (re-issue later) retires the number now and the payment goes back to waiting. Once the details are right, Issue 18A sends the replacement with a new number.
5. Donors can start this themselves: Request correction on their portal tells you what’s wrong, and you’re notified.

1. Donations aren’t refunded. When money still goes back (a mistaken amount, a duplicate payment, a card chargeback), SARS needs the certificate cancelled, so press Record reversal on the donation’s row. It’s for money returned in full.
2. If the gift has a certificate, it’s voided permanently (that donation can never be certified again) and only the SARS Representative can record it. An uncertified gift can be recorded by whoever reconciles.
3. The payment keeps the day the money came in; Transactions shows the money going out on the day you recorded it.
4. The Reversed / void tab lists them, and the audit trail keeps who, when and why.

Refunding a paid place is different: How do I refund a paid place?

1. Nothing to do: when a paid place is paid, kaycie issues the invoice (one per charge for monthly places) and emails it to the payer.
2. Find every invoice on Sales: view, print or download the PDF. It says TAX INVOICE (with VAT) or INVOICE, following your VAT position.
3. Paid straight into the bank? Use Record an EFT sale payment on Sales: pick the enrolment, enter the amount and date, and the invoice is made just as for a card payment.
4. A contact who pays (a parent, say) gets their own My invoices page: their invoices, what’s owing, pay online, tax invoices and any credit notes. An organisation that pays is emailed its bills and invoices instead.

Why: a sale never gets an 18A, and a donation never gets a VAT invoice. kaycie refuses the wrong one.

Billing a paying student, reminders and part payments: How do I bill a paying student?

1. Choose under VAT position on Setup, with your accountant.
2. Payment basis (the default): a tax invoice for each payment as it arrives.
3. Invoice basis: the tax invoice is issued with the bill, and part payments count against it. A monthly place gets one invoice a month. Cancelling an unpaid bill issues a credit note.

1. On Sales, open the payment’s ⋯ menu and press Record refund. Say why (it goes on the credit note), then confirm.
2. kaycie records the refund and issues a credit note against the invoice, with its own number, emailed to the payer and kept with your documents. A bill paid in parts is refunded one payment at a time.
3. Transactions shows the money going out on the day you recorded it, with the VAT reversed.
4. kaycie only records the refund. Pay the money back yourself, through your bank or PayFast.
5. The student stays enrolled until you withdraw them on Programmes. If the place is paid monthly by card, cancel the subscription in PayFast as well.

1. Submit the quote on Spending: supplier, amount, invoice number, what it’s for, and the quote PDF.
2. Above your two-quote threshold, capture each competing quote as its own entry under the same job name, or record a sole-supplier justification (every use is logged for the board).
3. A different person approves it with a typed signature, within their approval limit. Larger amounts need a second signature from someone else again. By default you can’t sign off your own submission (Approval rules).
4. If kaycie flags a possible duplicate (the same supplier’s invoice number or amount seen recently), approving it needs an override reason.
5. Quotes waiting longer than your set number of days show in notifications by themselves.

1. Once approved, capture the supplier’s invoice against the quote. A quote can be invoiced in parts (deposits, progress billing). The same invoice number from the same supplier is refused twice, ever.
2. The invoice is what reaches Transactions: on the invoice date (accrual) or when the payment leaves your bank (cash), whichever basis you set.
3. Pay from your bank as usual, then record the payment on the invoice with the proof. If the supplier’s bank details changed since they were last verified, kaycie refuses until a second person verifies them again. Paying before delivery is your call (a deposit is normal); kaycie notes it for the board.
4. When the goods or services arrive, the submitter or a signer presses Confirm delivery (it doesn’t hold up payment). The file is complete: quote, approval, invoice, payment, delivery.

1. An invoice above the approved amount (beyond the tolerance) can still be captured by someone with Admin & setup access, with a short reason (a variation order, a rate change, delivery costs).
2. It’s recorded as an exception the board sees, the reason shows to whoever pays, and nothing is held up.
3. Anything still unfinished waits on Needs attention, under Still open.

1. Choose the PDF on the quote or invoice form and kaycie reads it: the total, the VAT, the invoice number, the date and the supplier’s VAT number. It fills only empty boxes and marks each one in amber.
2. Nothing is saved until you press save. Check each amber box against the document and change anything wrong. The audit trail keeps what was read beside what you saved.
3. It warns you when the invoice number is already on file, and when an invoice asks for more than the approved quote.
4. PDFs from an accounting package are read on your own site; nothing leaves it. Photos and scanned PDFs have no text to read: fill those in yourself, or your organisation can switch on an AI reader under Admin & setup → Spending controls (off unless you choose it; supplier documents only).

1. Bank details are captured by one person and confirmed by a second, never typed into an ordinary form. Every proof uploaded files in the Vendor bank-proof archive.
2. A changed account number blocks payment until someone verifies it again. That pause is the fraud control working.
3. It’s enforced unless your organisation turns it off under Approval rules; unverified payments are then marked on the record.
4. In solo mode the one person handling money may verify details they captured themselves, and the record says so. In shared mode it must be someone else.

1. Every supplier gets their own signed link: no account, no password. They send quotes, invoice approved work and see progress. Each supplier’s link lives on their row.
2. Gone quiet? Under Signed off, a quote with no invoice yet has Ask for the invoice in its ⋯ menu. Under Vendors & bank verification, a supplier with no banking details (or details not yet verified) has Ask for banking details.
3. Each emails them a link to their own supplier page, at the email on their organisation record (add one on Contacts → Organisations first). Each reminder can go once a day; kaycie never sends them by itself.

1. Share /submit-a-quote/ anywhere.
2. A new supplier’s first quote creates their supplier page automatically.
3. Returning suppliers can ask for their private link from the same page.

1. Open Bulk import on Spending and paste or upload your CSV: one expense per line (supplier, amount, invoice number, what it’s for, programme).
2. Rows kaycie can’t read are skipped and listed with the reason, never guessed.
3. Each row lands as a draft: attach the quote or invoice, check the figures, then Submit. It goes through the normal sign-off checks, duplicate detection included.

1. Reconcile any EFT donations first, on Donations, or import the bank statement.
2. Open Transactions and pick the period (last month, say). Income shows every recorded payment; expenses show every supplier invoice, dated on your accounting basis; manual entries sit among them.
3. Regular payments (rent, salaries, the things that recur) are recorded under Regular payments rather than typed again every month.
4. Download the CSVs and send them. These are your books of first entry, receipts attached; your accountant reconciles them to the bank in their own system. Every export is the complete set, with no row cap.

Twice a year, add the IT3(d) file for SARS; at year-end, the funder packs for your funders.

1. Every expense line has a Category box. Type what it is: salaries, rent, programme materials, whatever your accountant uses.
2. It’s free text, with no list to set up. Once you’ve used a word, the box offers it back, so the same category is spelled the same way every time.
3. Type down the whole column, then press Save categories once. The line beside the button says how many expenses still have no category: check it before you export.
4. The category is a column in the CSV, which is the part your accountant asked for.

Why: coding happens here, at month-end, not when a quote is captured. The person capturing a quote (often the supplier) doesn’t know your chart of accounts. You do. It’s kept with the purchase, so changing basis never means coding twice.

1. A grant paid straight into the bank, fuel on the treasurer’s card, a market-day cash collection: open Money that moved outside kaycie on Transactions.
2. Record it as money in or out, with the date, amount, a category and, if it belongs to one, the programme. It joins the Transactions lines, the CSV and the budget’s actuals straight away.
3. Donations, paid places and supplier invoices already count from their own pages. Enter them there, not here, or they’re counted twice.
4. A removed entry stays on the record as removed; the audit trail has both.

1. Accrual counts an expense when the supplier invoices you. It’s what annual financial statements and an audit expect, because it shows what you owe, not just what you’ve paid.
2. Cash counts money when it moves, so your transactions line up with your bank statement.
3. Pick the one your accountant uses, once. Transactions, programme money and forecasts all follow it. It’s separate from the VAT invoicing basis, which is about tax invoices on income.

1. Open Budget under Finance. Pick the financial year (it starts in the month you set: March by default, the South African tax year) and the whole organisation or one programme.
2. Add a line per category: expense lines use your spend categories (Salaries, Rent, Programme costs…), income lines use the income types (Donations, Sales). Saving a category that already has a line updates it.
3. Beside every line is the actual to date, from the same Transactions lines and categories. Anything recorded this year with no budget line yet is listed underneath, one click to budget it.

Why: budget and actual use the categories your bookkeeper codes on Transactions, so they can never disagree about what a rand was for.

1. Transactions opens with the pacing line (68% of budget spent, 7 months in) for the whole organisation and for each programme with a budget.
2. It compares the share of budget spent with the share of the year gone: on track, ahead of pace, or under pace.
3. Budget vs actual on Reporting lays every line beside what came in and went out, with the variance, and exports to CSV for the board pack.

1. The chair or secretary drafts it on Compliance. Start from a template (bank accounts, directors, loans, big spends, MOI changes) or write your own, and pick the threshold: ordinary, special (75%), unanimous, or the custom percentage your MOI states.
2. Open it for signing. Every board member with signing rights gets a kaycie email and votes approve, reject or abstain with their typed full name. One vote each, no edits after.
3. The moment the outcome is certain, kaycie closes it, gives it a minute number (RES/2026/…) and files the signed minute PDF in Documents.
4. Missed the vote? Add my signature still works afterwards. The outcome never changes; the minute is made again with the fuller signature table.
5. Changed course? Withdraw a draft or open resolution from its ⋯ menu. Signatures already given stay in the audit trail.

Every open resolution shows who still must sign. The Resolutions register (CSV) is the auditor’s one-page answer to “show me every board decision”.

1. When drafting, switch to Meeting record: capture the date, attendance and vote counts, and sign as chair.
2. One other signatory countersigns to close it.

1. Give each board member the Board Member tick on Admin & setup → Team members → Edit access.
2. That tick grants signing access, so nobody is locked out of a vote.

1. On Compliance, press Record a meeting: type, date, who was present, apologies and the record itself. Save as a draft while you tidy it.
2. Press Finalise when it’s complete. The minutes get a permanent number (MIN/2026/…), a PDF files itself in Documents, and nothing can edit them again: your 7-year retention, by construction.
3. Passed resolutions have their own minutes (RES/…). Link them by id so the meeting record refers to them formally.

1. Fill in Your registration dates once, on Setup: CIPC registration date, financial year-end (or Not sure yet, fine for new organisations), and whether you’re a registered NPO. After that every deadline works itself out, every year.
2. Built in: the CIPC annual return (with beneficial ownership) in your anniversary month, from the year after you registered; the DSD report nine months after year-end; and SARS IT3(d) by 31 October (1 March to 31 August) and by 31 May (the full tax year).
3. Add your own recurring deadlines too (a funder report, an insurance renewal): set once, repeated every year.
4. Anything within 30 days also arrives as a notification. When you’ve filed, press Mark done. It’s in the audit trail, so “did we file?” always has an answer.

Why: missing two CIPC annual returns in a row risks deregistration. The calendar exists so that can’t sneak up on you.

1. Open CIPC annual return on Compliance. It opens itself 120 days before your return is due and shows the order CIPC wants: the beneficial-ownership declaration first, then your financial statements (or the FAS), the compliance checklist, then the return and its fee.
2. Check who to declare. Answer Members besides the directors? under Your registration dates once. With no members, CIPC accepts your directors. Each person needs an ID copy certified within the last three months.
3. Press Draft the mandate resolution. CIPC needs a signed mandate naming the person who files, signed by more than half of the directors. Fill in the filer’s details, open it for signing, and upload the signed minute with the declaration.
4. Note the fee. Kaycie shows it from your cash-book income and the date the lower fee ends, 30 business days after your anniversary. Use the turnover from your financial statements if it differs.
5. File on CIPC eServices or BizPortal yourself (CIPC has no filing service other than its own websites), then press Record the filing on Compliance: the date, the CIPC reference and the certificates. The deadline ticks itself done and the certificates land on Documents.

Why: since July 2024 CIPC refuses the annual return until the beneficial-ownership declaration is in, and both are needed every year. Arriving with everything in hand turns an afternoon of hunting into a few minutes.

1. Find it on Documents and click Download. kaycie checks you’re allowed to see it, then gives you a short-lived secure link.
2. Links expire in about two minutes and work once. If one expires, click Download again.

Why: these files carry personal information, so there’s never a permanent public link to any kaycie document.

1. Open Upload a document: policies, signed leases, your constitution, anything worth keeping under lock.
2. It lands in the same gated storage as the documents kaycie makes: no public links, single-use downloads, all logged.
3. Tick needs a signature and it appears in the signing picker.

1. Open Document templates and start from the library: volunteer agreement, funder MOU, guardian consent letter, donation letter.
2. Edit the wording in your own voice, then Generate. It’s made as a PDF straight into Documents, ready to be signed if the template needs it.

1. On Documents, open Sign a contract and pick the document waiting for you.
2. Sign with your typed full name and the I agree tick. It’s ECTA-compliant and logged in the audit trail.

1. Finance overview on Reporting shows the financial year so far: money in and out, by category and by programme, with the budget pacing beside it. Print it whenever you like.
2. After each month closes, kaycie files a monthly summary to Documents by itself: the month, the categories, the programmes and the year to date.
3. It’s mentioned in the monthly oversight message and in the bell, never as an email of its own, and it waits until a full month of data exists.

1. Open IT3(d) return on Reporting. It downloads the 18A donation data for your accountant’s IT3(d) returns to SARS.
2. There are two a year: by 31 October for receipts from 1 March to 31 August, and by 31 May for the full tax year (1 March to the end of February).
3. Each button shows its dates and due date. The 1 March to 31 August file is the latest one that has ended; the full-year file is the year just ended until the end of May, then the current one.
4. A revoked certificate drops off by itself, and its replacement takes its place.
5. The last column, needs attention, lists anything SARS would turn away, such as a missing postal address or a tax number that fails SARS’s check. Fix it on the donor’s 18A details, then download again.

Why: SARS asks for these details in this order and these codes, so your accountant can file from it.

1. First set the funder on the programme. Its enrolments take the funder from there.
2. On Reporting, open the Funder evidence pack, pick the funder organisation and the dates it covers (leave them empty for all time).
3. Open the pack: the students served, enrolments and outcomes, the programmes funded and the amount received, with the tamper-evident trail behind them. Print it, or save it as PDF.

1. Pick a report template and a period. kaycie sums up the answers per programme: averages, counts per option, and change against the previous period.
2. Aggregate figures only: no names ever appear, and groups smaller than the small-group threshold are left out entirely, so nobody can be identified by elimination.
3. Five is the default. Set it once on Admin & setup → Small-group threshold; it applies to every summary, story and funder pack.
4. Add your comments when you generate. They live on the document, not in the data.

1. Open Audit trail and search or filter by action, record type or date. A number finds that record or user.
2. Press Verify the chain any time: kaycie recomputes every entry’s fingerprint against the one before it. Every hash intact means nothing has changed since the day it was written.

Why: entries can never be edited or deleted, not even by an admin. This is the trail behind every 18A certificate, approval and payment, made as you work: you never prepare for an audit, you open this page.

1. Press Audit log (CSV). The export includes the hashes, so an auditor can check the chain independently. The export itself is logged too.
2. For anything contentious, the live audit trail is the authoritative record.

1. How many people handle money? One sets solo mode: the approval checks stay on screen but are logged rather than enforced, and a self-approved quote reads self-approved, solo mode on the record.
2. Two or more sets shared mode: nobody signs their own submission, and changed bank details need a second person. The audit trail and the 18A checks never relax in either mode.
3. Do you charge for any programmes? Yes switches on Sales, paid places and VAT invoicing. No, or not yet, leaves Sales off, so it never shows until you want it.
4. Both answers go in the audit trail. Change them later on Setup (or the mode on Approval rules).

1. Open Setup from the card on Home, or from Admin & setup at the foot of the side menu. The top counts the required steps (4 of 7 done) and lists what’s still open.
2. Work down the list. Each row says what it unlocks: PayFast unlocks card donations, bank details unlock EFT donations with a reference, your registration dates unlock the deadlines, and the property consent record lets the media library clear photos of your own premises with no one in them.
3. Optional steps (your brand colours, your own wording, the seat-release default) show an Optional chip and never hold the count back.
4. Once every required step reads Done, the setup card leaves Home. Setup stays there for whenever something changes.

Why: setup is what lets the rest run by itself: PayFast makes donations verify themselves, the VAT position makes invoices right, and the 18A switch is the gate SARS expects you to control.

1. On Setup, open Organisation details & 18A status: your name, NPC/NPO numbers, PBO/18A reference and signatory.
2. Tick SARS 18A approval confirmed only when you hold the SARS letter. No certificate can be issued until you do.
3. Set the reply-to address here too. It’s where a donor’s reply to any kaycie email arrives, so make it a mailbox someone reads, never a no-reply.

Why: every 18A certificate, invoice and minute prints these details.

1. On Setup, open PayFast (card payments). Paste the values from your PayFast account, and set your processing-fee rate (for the optional “cover the fee” tick on donation forms).
2. Do a small test donation to check it works end to end.
3. kaycie never sees a card number: the payment happens on PayFast’s side and comes back confirmed. Leave PayFast blank and you run on EFT only.

1. On Setup, open Bank details (EFT) and enter your bank, account name, number and branch code.
2. Donors who choose EFT on the donate form see them with a unique payment reference. They also print on invoices, so check them carefully.
3. Every change to these details is logged, because they’re a fraud target. Leave the account number empty to switch the EFT option off.

1. If you’re registered: on Setup, open VAT position, tick VAT registered, confirm the rate and enter your VAT number.
2. Mark a VAT-exempt programme as exempt with its fee, under Paid places. Your accountant’s call.
3. Fees never change for the student; only the invoice breakdown does.

1. On Setup, open Your logo: upload your logo, or paste a link to one, and choose a brand colour for the email header and button.
2. 18A certificates, invoices and invites then arrive in your look. Until you add a logo, emails show your organisation’s name.
3. Your brand colours (optional) put the donate form, wishlist and the donor, guardian and invoice portals in your colours. Staff dashboards keep the kaycie look.

1. On Admin & setup → Team members, press Add a team member and enter their name and email.
2. Tick the boxes for what they do: one box per dashboard, and ticking it grants what that dashboard does. Leave Give access & email an invite ticked, or untick it to record someone as team without a login.
3. They get a set-password email and see only what you ticked.
4. A few boxes carry authority, not just access, like the SARS Representative, who can issue 18A certificates. Give those deliberately.

1. Everything happens on the person’s own row: Edit access, Send invite (for people recorded without a login), Remove access or Remove completely. Changes apply straight away.
2. Remove access keeps their login, so they can be given access again later.
3. Remove completely takes them off the list and deletes their login, which frees their email for someone else. Use it for someone who has left, or who was added by mistake and never started.
4. Either way their contact record and everything they did stays: kaycie never erases history. Every invite, change and removal is in the audit trail.

1. The person responsible for your payments gets their own tick, Money alerts. It sends the payment emails: money received by card or EFT, and promised EFT donations to watch for on the bank statement.
2. Owners and Admin & setup always receive them. Plain Donations & Sales access doesn’t email.

1. Under Admin & setup → Approval rules, three tickboxes decide what’s a hard stop: approving your own submission, paying a supplier whose bank details changed unverified, and paper-only medical and transport consent.
2. Ticked, kaycie stops the action. Unticked, it goes through and the reports show who did what. A one-person organisation can untick self-approval and work normally; the spending download then shows self-approved against those rows.
3. Solo or shared mode sits at the top of the same panel. In solo mode the two money checks are logged rather than enforced, whatever the tickboxes say; the consent tickbox keeps its own setting. Switch to shared the day a second person starts handling money.
4. Every change to these tickboxes is written to the audit trail: who, when, from what to what.
5. The amounts (the second-signature threshold, minimum quotes and per-signer limits) are under Spending controls, just below.

Why: why a check is off is a question your committee asks a person. kaycie keeps the facts ready.

1. Admin & setup → Your kaycie package shows what your package includes and what the others add.
2. Upgrades open the new tools straight away; the new price starts at your next billing.
3. Downgrades keep everything until your next billing, then the lower price and smaller toolset apply together.
4. Cancelling keeps your workspace open to the end of the period you’ve paid for, and your exports keep working.

Why: nothing you’ve recorded is ever deleted by a change of package. Tools close, records stay, and they reopen the moment you move up again.

1. Layout sits in the same panel: the side menu, or the classic layout with the Menu button at the top and the Home cards.
2. It’s one setting for the whole team. Donors, guardians and payers see their own portals either way.

1. Open Admin & setup → Reminders & deadlines and give it a title and message.
2. Pick who it reaches (everyone enrolled in a programme, all donors, all volunteers, the team, or everyone) and when (on a date, some days before it, or weekly or monthly).
3. Before it ever goes out, the list shows exactly how many people it reaches.
4. It arrives in-app and as a branded email. People who opted out of email are skipped, and every send is logged.

1. On Setup, open Messages & wording.
2. Edit any email, page or form thank-you text in plain language. Reset to default any time.

1. Contacts: supporters sign up and update their own details; organisations register themselves.
2. Donations: donors give through your donation link (their EFT then matches itself) and ask for their own 18A on the donor portal.
3. Sales: payers pay online from the bill email, or on My invoices.
4. Spending: new suppliers send their own quote; existing suppliers send invoices and bank details from their own page.
5. Students: guardians consent online through Request consent.

Why: wherever you’d type something in, a gold tip offers the link so the other person does it instead, and gets it right. On Transactions, the tip reminds you that donations, paid places and supplier invoices arrive on their own.

1. Setup → Your links holds every address and embed you hand out: the donate form, sign-up, the public quote page, the wishlist. Anything not live yet says so on its row, like the donation link before PayFast or bank details are set up.
2. Each link has Copy, WhatsApp, Email, Open and QR code (save the picture for a poster or collection tin).
3. The donation link is the one to put in an email, on your website, or behind a QR code on a flyer.
4. Got it hides a tip for you; Show them again, under Your links, brings hidden tips back.

The student form has no public link on purpose. It stays staff-only, for safeguarding.

1. Donors with an account sign in and see My donations: every promised and received donation.
2. They press Request 18A on a payment’s row and download the PDF once it’s issued. Spotted a mistake (an old address, a wrong tax number)? Request correction tells your team, and it’s re-issued under a new number.
3. They update their own details. kaycie applies the change and logs the old value, so your team can see (and restore) it.
4. They see each supported programme’s summary, raised against put to work, live: the same figures as your programme statements.

Why: donors who gave through your Donate form with an email get their portal login automatically. Nothing for you to set up.