Follower Status Lifecycle
Every follower relationship in FeatsClub has a status that represents the current state of the connection between a user and your organization. This page is a comprehensive reference for all follower statuses, community roles, and follow modes -- everything you need to understand how the system tracks and manages these relationships.
Status Lifecycle Overview
Follower status changes are driven by actions -- either from the organization admin or from the user. Understanding the lifecycle helps you predict what will happen when you approve a request, block a follower, or mark someone as alumni.
User-Initiated Flow
When a user discovers your organization and taps Follow, the lifecycle begins:
User taps "Follow"
│
v
┌───────────┐
│ Requested │ (Pending -- appears in your Requests tab)
└─────┬──────┘
│
┌────┴─────┐
│ │
v v
Approve Reject
│ │
v v
┌──────────┐ ┌──────────────┐
│ Accepted │ │ OrgRejected │
│ (Active) │ │ (Blocked) │
└──────────┘ └──────────────┘
When auto-accept is enabled, follow requests skip the Requested stage entirely. The user goes directly from tapping "Follow" to Accepted status -- they appear in your Active tab immediately with no manual intervention required.
Org-Initiated Flow
When you proactively invite a user to follow your organization:
Org sends invitation
│
v
┌──────────┐
│ Invited │ (Appears in your Active tab as pending acceptance)
└─────┬─────┘
│
┌────┴──────┐
│ │
v v
User accepts User declines
│ │
v v
┌──────────┐ ┌────────────────┐
│ Accepted │ │ MemberRejected │
│ (Active) │ │ (Declined) │
└──────────┘ └────────────────┘
Post-Acceptance Transitions
Once a follower is in Accepted status, several transitions are possible:
┌──────────────────────────────────────────────────────────┐
│ Accepted (Active) │
└──────────┬──────────────┬──────────────┬─────────────────┘
│ │ │
v v v
Mark Alumni Block Change Role
│ │ │
v v v
┌──────────────┐ ┌──────────────┐ Same status,
│ PastAccepted │ │ OrgRejected │ new role
│ (Alumni) │ │ (Blocked) │
└───────┬───────┘ └───────┬───────┘
│ │
v v
Restore Unblock
│ │
v v
┌──────────────┐ User can send
│ Accepted │ new follow request
│ (Active) │
└──────────────┘
Complete Transition Map
Here is every possible status transition in one reference:
| Starting Status | Action | Resulting Status |
|---|---|---|
| -- (none) | User sends follow request | Requested |
| -- (none) | Org sends invitation | Invited |
| -- (none) | User follows (auto-accept on) | Accepted |
| Requested | Org approves | Accepted |
| Requested | Org rejects | OrgRejected |
| Invited | User accepts | Accepted |
| Invited | User declines | MemberRejected |
| Invited | Org cancels invitation | OrgRemove |
| Invited | Org blocks | OrgRejected |
| Accepted | Org marks alumni | PastAccepted |
| Accepted | Org blocks | OrgRejected |
| Accepted | Org changes role | Accepted (same status, new role) |
| PastAccepted | Org restores | Accepted |
| PastAccepted | Org blocks | OrgRejected |
| OrgRejected | Org unblocks | -- (user can re-request) |
| MemberRejected | Org re-invites | Invited |
Complete Status Reference
Every follower in FeatsClub has one of the following statuses. Each status determines where the follower appears in your dashboard and what actions you can take.
| Status | Display Name | Description | Dashboard Tab | Available Actions |
|---|---|---|---|---|
| Requested | Pending | User has sent a follow request and is waiting for your approval | Requests | Approve, Reject |
| Accepted | Active | Follower has been approved and is an active member of your community | Active | Block, Mark Alumni, Change Role |
| Invited | Invited | Your organization has invited this user; waiting for them to accept | Active | Cancel, Block |
| OrgRejected | Blocked | Your organization has rejected or blocked this follower | Blocked | Unblock |
| PastAccepted | Alumni | Previously active follower who has been marked as alumni | Alumni | Restore, Block |
| MemberRejected | Declined | User received your invitation but chose to decline it | (hidden) | Re-invite |
| OrgForget | Removed | Your organization has forgotten or removed this follower | (hidden) | -- |
| OrgRemove | Removed | Your organization has removed this follower | (hidden) | -- |
| Closed | Closed | The connection has been closed | (hidden) | -- |
| PastInvited | Past Invited | A previously sent invitation that is no longer active | (hidden) | Re-invite |
| PastRequested | Past Requested | A previously submitted request that is no longer active | (hidden) | -- |
| NA | Unknown | Default or unset status | (hidden) | -- |
Statuses marked as (hidden) do not appear in any tab on your follower dashboard. These are historical or system statuses that exist in the data but are not surfaced in the UI. You generally do not need to interact with them.
Dual-Write Architecture
When a follower's status changes, FeatsClub updates the record in two places:
- Organization side -- The follower record under your organization, which you see in your dashboard
- User side -- The user's own record of organizations they follow, which they see in their app
This dual-write ensures that both the organization and the user always have a consistent, up-to-date view of the relationship. All status changes, role assignments, and actions are written to both sides simultaneously.
Because of dual-write, changes you make on your dashboard are immediately reflected on the user's side. When you approve a follow request, the user sees the update in real time. When you block someone, their app reflects the change instantly.
Activity Logging
Every status change is recorded in the activity log on the follower's detail page. The log captures:
- What changed -- The previous status and the new status
- When it changed -- Timestamp of the action
- Who made the change -- Whether it was an admin action or a user action
This creates a complete audit trail for every follower relationship, which is valuable for accountability and for understanding the history of a connection before taking further action.
Community Role Reference
Every follower is assigned a community role that defines their level of access within your organization. Roles are separate from status -- a follower can be in Accepted status with any role from FOLLOWER to ADMIN.
Role Hierarchy
Roles form a progression of increasing responsibility and access:
FOLLOWER ──→ MEMBER ──→ COACH ──→ ADMIN
│
│ (Any active role can transition to Alumni)
│
ALUMNI
ALUMNI is not part of the linear hierarchy. It is a lateral designation that can be applied to a follower who previously held any role. An alumni member's previous role is preserved in their history.
Role Details
FOLLOWER
The default role assigned to every new follower.
| Aspect | Details |
|---|---|
| Access Level | Basic |
| Can View | Public content, public events, organization profile |
| Notifications | General announcements, public event promotions |
| Typical Users | Parents, supporters, casual followers, community observers |
| Assigned When | Automatically on first follow |
MEMBER
Active participant in the organization's programs and activities.
| Aspect | Details |
|---|---|
| Access Level | Enhanced |
| Can View | Everything a Follower can, plus member-only events and club activities |
| Notifications | All Follower notifications, plus member-only event invitations, class reminders, schedule changes |
| Typical Users | Students, athletes, enrolled participants, regular attendees |
| Assigned When | Manually promoted by org admin when enrolling in a program |
COACH
Instructor or group leader who manages activities within the organization.
| Aspect | Details |
|---|---|
| Access Level | Management |
| Can View | Everything a Member can, plus rosters and attendance tools for their assigned groups |
| Notifications | All Member notifications, plus attendance reminders, session alerts, roster updates |
| Typical Users | Teachers, trainers, instructors, team captains, workshop facilitators |
| Assigned When | Manually assigned by org admin for specific groups or programs |
ADMIN
Delegated administrator with elevated permissions to manage organization operations.
| Aspect | Details |
|---|---|
| Access Level | Administrative (based on delegated permissions) |
| Can View | Organization management features based on granted permissions across 7 categories with 40+ individual permissions |
| Notifications | All Coach notifications, plus new follower alerts, payment notifications, system updates |
| Typical Users | Assistant directors, office managers, department heads, trusted staff |
| Assigned When | Manually assigned by org owner with specific permission grants |
Admin permissions are granular and must be explicitly granted. Assigning the ADMIN role alone does not automatically give someone access to everything. You must also configure which specific permissions they receive through the Admin Delegation settings.
ALUMNI
Past member who maintains a historical connection to the organization.
| Aspect | Details |
|---|---|
| Access Level | Limited (similar to Follower) |
| Can View | Public content, alumni-specific communications |
| Notifications | Alumni-specific messages, reunion events, milestone celebrations |
| Typical Users | Graduated students, former team members, past program participants |
| Assigned When | Admin marks an active follower as Alumni via the Mark Alumni action |
Changing Roles
Role changes do not affect follower status. A follower remains in Accepted status regardless of whether their role changes from FOLLOWER to MEMBER, MEMBER to COACH, or any other transition.
| From Role | To Role | Effect |
|---|---|---|
| FOLLOWER | MEMBER | Gains access to member-only events and club content |
| MEMBER | COACH | Gains access to activity management tools for assigned groups |
| COACH | ADMIN | Gains access to org management features (based on delegated permissions) |
| Any role | ALUMNI | Moved to Alumni tab, active access reduced, history preserved |
| ALUMNI | Any role | Restored to Active tab with the assigned role |
Follow Mode Reference
FeatsClub tracks how a person is connected to your organization through the follow mode. This indicates whether someone is following the organization as a whole, a specific club, or a specific cohort.
Follow Modes
| Follow Mode | Description | Example |
|---|---|---|
| Org | Following the organization as a whole | A parent follows "City Dance Academy" to see all announcements |
| Club | Following a specific club within the organization | A student follows the "Hip Hop Club" for class schedules |
| Cohort | Following a specific cohort or program | A participant follows the "Spring 2026 Beginner Batch" for session updates |
Multiple Follow Relationships
A single user can have multiple follow relationships with the same organization, each with a different follow mode. For example:
- Sarah follows "City Dance Academy" (Org mode) AND follows "Hip Hop Club" (Club mode) AND follows "Spring 2026 Beginners" (Cohort mode)
- Each of these is tracked as a separate follower record with its own status, role, and activity history
This means:
- Sarah might be a MEMBER at the Org level but a FOLLOWER at a specific Club level
- Blocking Sarah at the Org level does not automatically affect her Club-level follow (though organizations can manage this)
- Each follow record has its own activity log
Follow mode badges appear on follower cards in your dashboard, making it easy to see at a glance whether someone is following your org, a club, or a cohort.
Follow Mode and Notifications
The follow mode affects which notifications a user receives:
| Follow Mode | Notifications Received |
|---|---|
| Org | Organization-wide announcements, all public events, general updates |
| Club | Club-specific updates, club event notifications, roster changes for that club |
| Cohort | Cohort-specific updates, session schedules, cohort event notifications |
A user following at multiple levels receives notifications relevant to each level without duplication.
Quick Reference Summary
Status at a Glance
| Status | Visible In | User Can See Org? | Org Can Contact? |
|---|---|---|---|
| Requested | Requests tab | Limited (pending) | No |
| Accepted | Active tab | Full access (based on role) | Yes |
| Invited | Active tab | Limited (pending acceptance) | Limited |
| OrgRejected | Blocked tab | No | No |
| PastAccepted | Alumni tab | Limited (alumni access) | Yes (alumni comms) |
| MemberRejected | Hidden | No | No |
| OrgForget | Hidden | No | No |
| OrgRemove | Hidden | No | No |
| Closed | Hidden | No | No |
Role at a Glance
| Role | Default? | Member-Only Access? | Can Manage Activities? | Can Manage Org? |
|---|---|---|---|---|
| FOLLOWER | Yes | No | No | No |
| MEMBER | No | Yes | No | No |
| COACH | No | Yes | Yes (assigned groups) | No |
| ADMIN | No | Yes | Yes | Yes (delegated permissions) |
| ALUMNI | No | No | No | No |
What's Next?
Return to the Tips & Best Practices overview for practical advice on applying these concepts. For details on setting up admin delegation and permissions, see the Admin Delegation section.