Available entities
Pour :Administrateur
An exploration is always built around a root entity: the main data type whose rows you want to see. This page lists the 7 entities available in Unisoft and gives concrete examples for each.
Overview
| Entity | What it's for | Typical examples |
|---|---|---|
| Contacts | CRM: directory of congregants, families, donors | Donors without email, contacts of a city, families with children |
| Payments | Individual collections | Large donations of the quarter, uncashed check payments |
| Pledges | Donation commitments | Unsettled pledges, pledges due this month |
| Subscriptions | Recurring commitments | Active subscriptions > €30/month, failed subscriptions |
| Form submissions | Registrations, requests via forms | Fair registrations, bar mitzvah requests |
| Interactions | Exchanges and notes with contacts | Calls made this week, contacts not re-contacted in 3 months |
| Tax receipts | Tax receipts issued | Receipts of the current year, unsent receipts |
Contacts
The central directory of your community: congregants, family members, donors, prospects, partners.
When to use this entity
- Prepare a mailing to a sub-population (e.g. donors of more than €500 over the year)
- Identify incomplete contacts (without email, without phone) for follow-up
- Segment by category or track for a targeted campaign
- List new contacts created this month
Main fields
| Category | Fields |
|---|---|
| Identity | Last name, first name, maiden name, Hebrew first name, gender |
| Contact | Phone, email |
| Address | Address, city, postal code, region, country |
| Categorization | Categories (tags), track/route |
| State | New, archived, Gift Aid |
| Dates | Creation date, modification date |
Exploitable relations
- Payments (of this contact) — collapsible sub-table
- Pledges (of this contact)
- Subscriptions (of this contact)
- Form submissions (of this contact)
- Interactions (of this contact)
Examples of views to build
- « Recurring donors with missing email » — contacts having at least one active subscription and whose email is empty
- « New contacts this month » — filter Creation date > 1st of the month
- « Cohen and Lévy families » — filter Name contains « Cohen » or contains « Lévy » (two separate views in V1)
Payments
All individual collections: online donations, cash donations, checks, transfers, in-kind donations.
When to use this entity
- Prepare a very targeted accounting export
- Check pending uncashed checks
- Track payments of a specific platform (Stripe, PayGreen…)
- List large donations beyond a threshold
Main fields
| Category | Fields |
|---|---|
| Identification | Identifier, label, comment |
| Date | Payment date |
| Amount | Amount, bank fees, organization fees, currency |
| Typology | Type (cash account, campaign, pledge, form, fund, event journey, booklet), method (Bank card, check, transfer, direct debit, cash, in kind), source (online, admin, app, donation kiosk…) |
| Platform | Stripe, PayGreen, PayPal, GoCardless… |
| Attachment | Payment reason (campaign, fund, pledge, form, event journey, booklet, main cash register) |
Exploitable relations
- Contact (associated to the payment) — inline
- Campaign, Fund, Pledge, Form, Event Journey linked
Examples of views to build
- « Large donations of the quarter » — Amount ≥ 100 €, Date between January 1 and March 31
- « Uncashed checks » — Method is « check », appropriate status
- « EUR payments of this year » — Currency is « EUR », Date after January 1
Pledges
The donation commitments (also called pledges). A pledge is an intention to donate to be honored, generally through one or several subsequent payments.
When to use this entity
- Identify unsettled pledges (remaining to pay > 0)
- Prepare a follow-up on due pledges
- Track pledges from a specific campaign
Examples of views to build
- « Unsettled pledges of the year » — Remaining to pay > 0, Year = 2026
- « Pledges due this month » — Due date before the end of the current month, Remaining to pay > 0
Subscriptions
The recurring commitments: monthly direct debits, recurring Bank card donations. A subscription generates several payments over time.
When to use this entity
- Track active subscriptions
- List failed subscriptions (expired card, refused direct debit)
- Analyze average amounts of subscriptions
Examples of views to build
- « Active subscriptions > €30/month » — Status is « active », Amount greater than 30
- « Subscriptions in error » — Status is « error »
Form submissions
All the responses sent via Unisoft forms (registrations, requests, surveys…).
When to use this entity
- Prepare the list of registrants for an event
- Analyze the response rate of a survey
- Identify incomplete submissions
Examples of views to build
- « 2026 Fair registrations » — Form is « Fair 2026 »
- « Pending bar mitzvah requests » — Form is « Bar mitzvah », status is « pending »
Interactions
The exchanges and notes related to a contact: calls, internal emails, appointments, comments.
When to use this entity
- List calls made this week
- Identify non-re-contacted contacts for a long time
- Track the activity of a team member on interactions
Examples of views to build
- « Interactions of the week » — Date after Monday
- « Calls about the collection » — Type is « call », comment contains « collection »
Tax receipts
The tax receipts issued by your organization. This entity is useful for checking the quality of the receipts before the annual declaration.
When to use this entity
- Prepare the annual tax declaration
- Check unsent receipts to the donor
- Identify receipts with errors (missing address, invalid amount)
Examples of views to build
- « 2025 Tax receipts » — Year is 2025
- « Unsent receipts » — Send status is « unsent »
Going further
- Create an exploration — build your first view
- Filters and sorts — available operators
- Save and share a view — private or org-wide