Orgo guides

Create the chapter, decide where it sits in the chapter tree, then grant chapter-scoped permissions. The part everyone gets wrong is the anchor rule: a chapter-scoped grant is not aimed at a chapter you pick, and for an ordinary chapter it starts one level up and covers that chapter's siblings.

Build a newsletter signup widget in Orgo, paste one snippet into your own site, and subscribers land in your contacts ready for the next campaign. The part that surprises people is the confirmation email: an address that never clicks the link is never subscribed and cannot be fixed by hand afterwards.

Create it under Lists and Segments, choose automated or manual once and for good, then add criteria that always combine with AND. The number that matters is Subscribed, not Total, because members and contacts carry separate subscription state and contacts start out opted into nothing.

Create a campaign, pick one audience from the five on offer, design it, then send or schedule it. The three things that catch people out are which audience actually resolves to whom, why the scheduler refuses a time that looks fine, and what the report numbers really count.

Automations are called workflows. One trigger, one of three actions, an optional delay. The three actions are send an email, add a tag and remove a tag, and the tag is the one that compounds, because a tag added by a workflow becomes a list criterion and therefore an audience.

Wording is edited in Email Templates. Stopping an email is a different screen, and changing who receives it is a third. Four independent off switches exist and only one of them applies to any given email, which is why this is the most confusing area in Orgo.

Point a camera at the attendee's QR code, read the card that opens, and tap Check in. Their RSVP becomes Attended. The one thing to settle before doors open is who is allowed to scan, because the chapter-level events permission is not enough on a plain phone camera.

Open Events, choose Create an event, fill in the form and save. It is created as a draft that only managers can see, and goes live when you press Publish Event. Three separate gates decide who may create an event where, and the third one fails silently.

Open the event's Participants screen. Then read the right column: registration status and RSVP are two different statuses, and reading one when you meant the other is the most common reason an attendance figure comes out wrong.

Connect Stripe, set the event's Access to Paid, then add ticket types under Tickets in the event sidebar. Member and non-member prices are two ticket types scoped to different audiences, not one ticket with a discount code, and getting that backwards is the single most expensive mistake on this screen.

Switch Enable VAT on Fees on in your membership fee settings, then set a rate on each membership price. Prices are always entered net and VAT is added on top. The joining fee is a separate switch, it is charged once per member and a returning member is never charged it twice.

Create invoice, pick one payer, enter the line, set the dates, save. Saving numbers the invoice, renders the PDF and emails it to the customer. The part that catches people out is later: marking an invoice as paid emails the customer too, so tidying up historical records sends real email to real people.

There are three places to record a bank transfer, cash or cheque payment, and they are not interchangeable. Pick by what was paid for: an invoice, a membership fee period, or anything else. Ticking, saving, marking as paid and pressing Pay are four different actions, and knowing which one actually settles the member is the whole job.

Create a product of type Donation, choose one-off giving, monthly giving or both, add suggested amounts, and the campaign gets a public page nobody has to log in to use. Two things surprise people: Orgo does not issue tax receipts, Stripe does and it has to be switched on, and donors land in your contacts rather than your membership.

Four things in order: create a Membership Fee product with its period, add one price per membership level, point your organisation at that product and a default price, then set who is eligible and how renewal works. Nothing charges anybody until the third step is saved.

Connect your own Stripe account in the online payment settings and money lands in your own bank account. Orgo never touches card data and takes no commission. The part worth reading twice is chapter routing, which is why a chapter's dues sometimes settle in the national account.

Five different things produce this symptom, and only one of them is a payment problem. Work through them in this order: the year filter, whether a payment was actually taken, account status, a live subscription, and the fee period.

Every group comes off the same form. What makes them different is the Access mode: auto-enroll, open to join, private or role group, plus units for permanent subdivisions of a chapter. Pick the mode first, because it decides who ends up in the space and who can see it.

Create the field once, then put it on a form. The setting that decides everything afterwards is visibility, which has three levels and controls both reading and writing. Anything above Public collects nothing at all through your public registration page.

Four routes get a person into your organisation: register them yourself from the member directory, send an invitation, let them sign up at /register, or import a spreadsheet. Pick by how many people you have and who fills in the details.

Set the application to Adhesion success in the adhesions queue. Then change the account status to Active, because approving an application never does that for you, and an approved member with the wrong status still cannot sign in.

Search and the filter row answer a question once. A saved list keeps answering it. The CSV export takes the answer out of the platform. Which one you need depends on whether you are looking something up, sending something, or working offline.

Save each sheet as its own CSV, put your old system's identifier in a user_legacy_id column, upload it on the Users step, then read the per-row errors. Nothing is written until the headers pass validation, and a completed import can be rolled back once.

Pick which record goes away and which one you keep, settle the conflicting fields, and confirm. Event registrations, payments, invoices, roles and adhesions move to the record you keep. Sign-in material is destroyed rather than moved, and you have one 30-day undo.

Open the Registration Form page in your settings, drag the fields you want onto the form and save. Two things catch people out afterwards: a profile field marked Required does not always prompt anyone, and only Public custom fields survive registration.

A user type categorises a member and can decide their fee and their registration form. A role carries permissions. They are created on the same screen and look almost identical, which is why organisations create a user type called Managers and then find that nothing was granted.

Members install Orgo Community from the App Store or Play Store and sign in with their normal credentials. The app is the same interface as the web, plus push notifications and links that open in the app. Three things it will not do: take a fee payment on iOS, record audio or video, or work offline.

Every permission is a domain paired with a scope, and it can reach a member from two independent directions: attached to a role, or ticked on their profile. Understanding that pair, and the rank rule that decides what you are allowed to hand out, resolves almost every permission question.