← All features

Members · Membership & Access

Who can do what, decided once.

A tier is a set of answers about a kind of member: what they can sign up for, how often, at which of your buildings, and what they see in the portal. Every module reads the same answers.

What it helps with

What your team can do here.

Member tiers

Nothing is switched on until you switch it on.

NestPoint starts you with Public, Member, and Suspended, and you rename them to whatever your organization says out loud. Then you go down a list of plain questions for each one. Can this person register for a class. Book a room. Request a ride. Sign up for a shift. Pay from their phone. Edit their own profile. That list is all a tier is, which is why it carries no price and no expiry date: a tier says what someone may do, not what they paid.

  • Public, Member, and Suspended to start, renamed to your vocabulary
  • One permission at a time across programs, rentals, rides, trips, meals, and shifts
  • Deny by default, so a blank setting is never an open door

Limits that hold

Three rides a month means three.

A tier can cap how often a member does something in a rolling window: ride requests, trip sign-ups, room bookings, shift check-ins, class registrations. The count is checked the moment they ask, not discovered in a report a quarter later. Leave a cap empty and there is no cap.

  • Rolling windows measured in days, not calendar months
  • Enforced at the request, not found afterward
  • Empty means unlimited

More than one building

A membership that works downtown may not work at the north site.

If you run more than one center, the tier says which of them a membership admits at. Someone whose tier does not cover the building they walked into is not turned away with a shrug. The desk says the membership does not include this location and offers a day pass instead. A tier with no centers listed works everywhere, which is what keeps single-site organizations from having to think about any of this.

  • Center access set per tier, plus the member's own home center
  • A day pass is the paid alternative, offered right at check-in
  • No centers listed means every center

Acting on behalf

Her daughter can book the ride. She cannot read the file.

Link two members and grant exactly what one may do for the other: register for a trip, pay for a class, request transportation, book a room, clock in for a shift. Fifteen actions, each its own yes or no. The grant runs one direction, so acting for your mother does not let her act for you, and it does not chain on to a third person. Revoke it and the record that it once existed stays.

  • Fifteen actions, granted one at a time
  • Parent, guardian, caregiver, spouse, sibling, friend, or other
  • One direction, no chaining, revocable without erasing the history

Active and inactive

Someone who stopped coming is still someone you know.

Marking a member inactive keeps everything: check-ins, registrations, payments, household, badge, notes. The front desk says so on the next scan instead of waving them through, and meal programs that require active status stop counting them. When they come back you reactivate the person you already had, rather than typing them in for the second time.

  • Nothing is deleted to change someone's status
  • The desk sees it on the scan
  • Imports read lapsed, expired, and former from your old system and land them as inactive

A typical workflow

One record, and the rules travel with it.

Check-in, the portal, the roster, and the ride list all ask the same record the same question.

  1. Decide what a member is. Go through the permissions once. Everything you do not switch on stays off, at the desk and in the portal both.

  2. Two front doors, two defaults. Somebody who signs themselves up in the portal lands on the tier you picked for that. Somebody a staff member creates at the counter lands on the tier you picked for that. They are usually not the same tier, which is the point.

  3. The portal shows only what fits. A member sees the things their tier lets them do. Nothing appears that they would only be told no about.

  4. A daughter books the ride. Her grant covers requesting transportation for her mother and nothing else. The request belongs to her mother's record.

  5. Someone stops coming. Mark them inactive. Eight years of history stay where they are, the next badge scan says so, and bringing them back is a toggle rather than a re-entry.

Common questions

What teams ask before getting started.

Set the rules once. Let the building follow them.

Bring the way you already sort people. See what happens when the desk, the portal, and the ride list all read the same record.

Card required. Cancel anytime.