Requests & Workflows

Structured approval processes for membership changes.

fellos uses structured workflows to handle membership changes. Instead of sending emails back and forth, all requests go through an organized approval process with built-in messaging. This means every request has a clear status, a full history of actions, and a paper trail that everyone can reference.

You'll find all workflow-related items in the Workflows section of the sidebar. Depending on your permissions, you may see links for Member Requests, Type Changes, Deactivations, and Transfers.

WORKFLOWS Member Requests 3 Type Changes 1 Deactivations Transfers Onboarding Request Request #1042 · Submitted by Alex Kim Pending New Member Details Name Jordan Martinez Email jordan.m@email.com Member Type Prospect Sponsor Alex Kim Organization Metro Chapter Submitted April 2, 2026 Activity Request submitted Alex Kim · April 2, 2026 at 9:30 AM "Jordan has been riding with us for 6 months and is ready to begin the prospect process." Documents uploaded Alex Kim · April 2, 2026 at 9:32 AM Application form and waiver attached. Awaiting approval from Chapter President System · April 2, 2026 at 9:32 AM Messages MR Maria Reyes 2 hours ago I've met Jordan — great candidate. I'll review and approve today. Approved Declined
The workflow detail view — showing a pending onboarding request with its activity timeline, status badges, and message thread.

Onboarding Requests

If your organization allows it, you can submit a request to bring a new member into the organization. This is how the structured onboarding process works:

  1. Navigate to Workflows → Member Requests in the sidebar.
  2. Click the New Request button.
  3. Fill in the new member's details: full name, email address, organization/chapter, and the member type they should start as.
  4. Select a sponsor (this may default to you, or you can choose another member).
  5. Attach any required documents — your organization may require a signed application, waiver, or other paperwork.
  6. Optionally add a message explaining why you're sponsoring this person.
  7. Submit the request for approval.

Once submitted, the request enters your organization's approval workflow. Depending on how your admin has configured things, it may need approval from a chapter president, a board vote, or multiple levels of review.

Tip

Include a detailed message when submitting onboarding requests. Reviewers appreciate context about how you know the person, how long they've been involved informally, and why you think they'd be a good fit. This speeds up the approval process.

Type Change Requests (Transitions)

When a member needs to change their membership type — for example, moving from Prospect to Full Member, or from Active to Retired — this is handled through a type change request (also called a transition).

Common transitions include:

  • Prospect → Full Member — After completing the probationary period
  • Full Member → Life Member — For long-tenured or honorary members
  • Active → Retired — When stepping back from active participation
  • Any type → Honorary — Special recognition

To submit a type change request:

  1. Go to Workflows → Type Changes in the sidebar.
  2. Click New Request and select the member whose type should change.
  3. Choose the new member type from the available options. Only valid transitions (as configured by your admin) will appear.
  4. Attach any required documents and add an explanation for the change.
  5. Submit for approval.
Good to know

Not all transitions are available to all members. Your admin defines which transitions are valid and who can request them. For example, only officers might be able to request a Prospect-to-Full-Member transition, while any member might be able to request their own retirement.

Deactivation Requests

When a member needs to leave the organization — whether voluntarily or through an administrative action — a deactivation request is submitted. Deactivation doesn't delete the member's data; it sets their status to inactive, removing their access while preserving their history.

To submit a deactivation request:

  1. Navigate to Workflows → Deactivations.
  2. Click New Request and select the member to deactivate.
  3. Provide a reason for the deactivation. This is required and helps maintain accurate organizational records.
  4. Submit the request. It will go through the approval process before taking effect.

Once approved and completed, the deactivated member will no longer be able to log in, and they'll move from the Active to Inactive section of the member directory.

Transfer Requests

Transfer requests move a member from one organization or chapter to another within the same fellos site. This is common in organizations with multiple chapters or regional divisions.

  1. Go to Workflows → Transfers.
  2. Click New Request and select the member to transfer.
  3. Choose the destination organization/chapter from the list.
  4. Add a message explaining the reason for the transfer.
  5. Submit for approval.
Important

Transfer requests may require approval from both the sending and receiving organizations. This means the request might take longer to process than other workflow types, as it needs sign-off from leaders on both sides.

Tracking Request Status

Every request you've submitted or are involved in appears in the Workflows section of the sidebar. Each request has a status that tells you where it is in the process:

  • Pending — The request has been submitted and is waiting for review. Shown with a warm sand badge.
  • Approved — The request has been approved by the required reviewers. Shown with a sage green badge.
  • Declined — The request was not approved. Shown with a terracotta badge. Check the messages for an explanation.
  • Cancelled — The requester withdrew the request before it was processed.
  • Completed — The approved request has been fully processed and the changes have taken effect.

Click any request to see its full detail view, including:

  • All the original request information
  • A timeline showing every action taken — submission, reviews, approvals, etc.
  • A message thread where you can communicate with reviewers and other involved parties
  • Attached documents and their status
Tip

You'll receive notifications when the status of your requests changes. Make sure your notification preferences are set up so you don't miss important updates. See the Notifications page for details on configuring alerts.

Messages Within Workflows

Every workflow request includes a built-in message thread. This keeps all communication about a request in one place, rather than scattered across emails or text messages. You can:

  • Add messages to explain or provide additional context for your request
  • Respond to questions from reviewers
  • See system messages that track status changes and automated actions
  • Upload additional documents mid-process if needed

Messages are visible to everyone involved in the request — the submitter, the subject of the request (if different), and all reviewers in the approval chain.