Transfers Between Orgs

How transfer requests work when a member moves from one organization to another.

Members sometimes need to move between organizations within your club — perhaps they've relocated to a new area, or they want to participate in a different chapter. In fellos, this is handled through a transfer request, which ensures both the sending and receiving organizations are aware of and agree to the move.

Transfers are one of the more complex workflow types because they can involve multiple parties. Depending on your site admin's configuration, a transfer may require approval from the sending org's admin, the receiving org's admin, or both.

How the Transfer Process Works

A transfer request moves through several stages:

1. Initiation — The member, their current admin, or the receiving org's admin creates a transfer request specifying the member, current org, and target org.
2. Sending org review — The admin for the sending organization reviews the request. They can approve, object, or add messages.
3. Receiving org review — The admin for the receiving organization reviews the request. They can approve, object, or add messages.
4. Completion — Once all required approvals are obtained, the member's organization assignment changes to the new org.

Reviewing a Transfer Request

When you open a transfer request from the "Transfers" queue, you'll see:

• Member details — The member's name, current type, and member number.
• From organization — The member's current chapter or org, with approval status from that org's admin.
• To organization — The target chapter or org, with approval status from that org's admin.
• Reason — Why the transfer was requested.
• Message thread — Communications between all parties involved.

Multi-Party Approval

Transfers are unique among fellos workflows because they can involve multiple approving parties. Here's how the multi-party process works:

Both Orgs Must Approve

In the most common configuration, both the sending and receiving organization admins must approve the transfer. The request shows the approval status of each party, and the transfer only completes when both have approved.

Objections

Instead of a simple "decline," transfer requests use an objection model. Either party can object to the transfer and provide a reason. An objection pauses the process and alerts other parties. The message thread becomes the venue for resolving the objection.

Order of Approval

There is no required order — either the sending or receiving admin can approve first. The system tracks each party's status independently. You'll see "Approved," "Awaiting Approval," or "Objected" next to each organization.

Override Capabilities

Higher-level admins have the ability to override objections and push a transfer through:

• Club Admin — Can override any objection and force-approve a transfer between any two organizations in the club.
• Org Admin — Can override objections for transfers between organizations within their scope. For example, a regional Org Admin can override an objection from one of their chapters.
• Local Admin — Cannot override. Can only approve or object for their own organization.

What Happens After a Transfer

Once all required approvals are obtained:

• The member's organization assignment changes to the new org immediately.
• They appear in the new org's member directory and disappear from the old one.
• Any officer roles they held at the old org are automatically removed.
• Their member type is preserved (they remain a Full Member, Prospect, etc.).
• Their complete history from the old org is retained and linked to their profile.
• The transfer is recorded in the member's history, showing both organizations and all approvals.

Cross-Region Transfers

Transfers that cross regional boundaries (e.g., from a chapter in the Northeast Region to one in the Western Region) are automatically visible to both regional Org Admins and to Club Admins. These transfers may require coordination between admins who don't normally interact, making the message thread especially important.