Skip to main content
Built for organisations whose audience is wider than their membership. Replaces a separate CRM or a spreadsheet of donors and subscribers. A contact is a person record without a login. Orgo creates one automatically whenever someone interacts with you without an account (buys a ticket, donates, subscribes to the newsletter), and you can add them by hand. Everything a contact does (payments, tickets, signed documents, emails received) stays attached to that record. Contacts directory with newsletter, status and tag columns and a search bar

​
Turning it on

Settings → Modules → Contacts → Enable Contacts Module (needs ADMIN_TENANT). Two extra switches live on the same page:

​
Who can see contacts

HR_TENANT and FINANCIAL_TENANT always see the full contact list. Local-level managers (HR_LOCAL, FINANCIAL_LOCAL) only reach contacts when Enable Per-Chapter Contacts is on, and then only within the local centers they belong to. When they create a contact without picking a chapter, it is filed under their own. Exporting the list to CSV requires HR_TENANT.
Contacts have no account and cannot log in to the member area. The one exception is the event app: a ticket holder who is a contact signs in with a one-time code scoped to that event only.

​
Where contacts come from

Every contact records how it arrived, shown as Source on the record and as a column in the list: To load contacts in bulk, use Settings → Import and pick the contact import type. There is no import button on the Contacts screen itself.

​
What a contact record holds

Adding or editing a contact gives you these fields: Saving a contact with an email that already belongs to another contact, or to a member, is rejected. Orgo tells you which of the two it clashed with. Contact record with Tags, Notes and Activity as stacked cards, the Notes card holding an Add a note about this contact box with an Action select, and the Activity card listing three Note added entries and a Donated 50 usd entry The record page adds panels that are filled in as the contact interacts with you: Status, Newsletter, Tags, Notes, Activity, Events, Payments & Subscriptions, Company Membership, e-Documents (when that module is on), Email logs, and an Identity link when they uploaded an ID document.

​
Notes and Activity

The Notes card writes a note; the Activity card below it is where notes are read, along with the contact’s donations, form submissions and tag changes on one feed. Both cards need Enable Profile Notes & Activity switched on and HR_LOCAL or FINANCIAL_LOCAL over that contact, or ADMIN_TENANT. Each note records its author and time, is capped at 512 characters, and carries an optional Called or Emailed action. Click a note in the Activity feed to read it in full, and to edit or delete it, which the person who wrote it or an ADMIN_TENANT may do. Older single-blob notes from before this change appear as notes without an author, so only an ADMIN_TENANT can edit those. Full detail: Profile Activity & Notes.

​
Statuses and tags

Statuses are a single-choice list you define under Settings → Modules → Contacts → Contact Statuses: name, colour, and drag-to-reorder. Tags are multi-choice and come from the shared tag catalogue used for members too, so you can filter the same tag across both.

​
Working with the list

Search matches name and email. The filter row adds Chapter, Status, Tags and Newsletter. Columns are Name, Country, Town, Chapter, Email, Phone, Newsletter, Source, Status, Tags, Date created and Stripe; most are sortable.
  • Select switches the list into selection mode for bulk delete.
  • Download CSV exports the filtered list 500 rows at a time. If the result is larger, Orgo asks which page you want. Every export is written to the audit log.
  • Per-row actions: Create user account, Open in Stripe, Delete contact.
A contact with a successful payment against it cannot be deleted, individually or in bulk. Bulk delete skips those rows and reports how many were skipped.

​
Newsletter subscription

The newsletter field on a contact has three states, and the list filter mirrors them: The Unsubscribe button shows only while the contact is subscribed, and using it requires HR_TENANT.
Unsubscribing takes effect immediately and the button disappears afterwards, so there is no one-click undo. Confirm the request before you use it.

​
Turning a contact into a member

Create user account on the contact record creates a member account from that email and sends the welcome email with a login link. The new member is asked to set a password on first login, and Orgo takes you straight to their member profile.
The contact record is kept as-is. It is not deleted, and its payments, tickets and documents stay attached to the contact rather than moving to the new member account. If you need the two records combined into one history, ask Orgo support to merge them.

​
Common questions

Donors without an account are contacts, not members. Search the Contacts list and filter by source Donation.
Yes. Newsletter audiences are built from both, and only contacts marked Subscribed are included.
Contacts are tenant-level unless Enable Per-Chapter Contacts is on and the Local Centers feature is enabled. Without both, only HR_TENANT and FINANCIAL_TENANT reach the list.
That is deliberate: deleting the contact would orphan the payment records. Keep the contact, or ask support if the payment itself needs to be removed first.
Creating a contact with an email that already exists is blocked, so duplicates usually differ by email. Fix the email on the record you want to keep, then delete the other.