Documentation

Private Property Donation

Private property donations can be small like a single fruit tree, or larger like an orchard or field. The instructions below are intended for non-farm properties. Documentation for Farm Donations is here.

Typical Workflow

The steps below outline the process for a private property donation.

Gleans here represent an event where people volunteer to gather produce so it can be distributed to people without reliable access to food.

Any signed-in user can create a new glean. Details about location are required.

If a team is assigned upon creation, team leaders will handle details from here. If no team is assigned, team leaders in the area will be notified of a pending gleaning opportunity.

A glean must have a location and team assigned to be submitted for approval by team leaders.

After a glean is created, it will saved as a "draft". Any user can submit a glean for approval by team leaders. If the glean is created by a user designated as team or distributor leader, the glean is auto-approved, proceeding directly to "approved" state.

Only "approved" gleans show on the website as opportunities for volunteers.

When a new glean is added, a notification is sent to the user who created it. If a team is designated, team leaders are also notified.

Click here to create a new glean

Once a Glean has been assigned a location and team, it can be submitted for approval. Team leaders will approve the glean when they are ready to schedule and facilitate it.

When a glean is submitted, an email notification is sent to the user who created it. Team leaders are also notified.

Gleans are approved by team leaders. Gleans must be approved before volunteers can sign up. Only approved gleans appear as opportunities for volunteering.

When a glean is approved, an email notification is sent to the user who created it. Team leaders and glean volunteers are also notified.

Gleans are "started" by team leaders. Only approved gleans can be started.

When a glean is started, an email notification is sent to the user who created it. Team leaders and glean volunteers are also notified.

Gleans are "finished" by team leaders. Only active gleans can be finished.

When a glean is finished, an email notification is sent to the user who created it. Team leaders and glean volunteers are also notified.

Harvests represent the product of a glean, or purchase of surplus food by a distributor.

Any signed-in user can create a harvest.

If the harvest is created by a user designated as team or distributor leader, the harvest is auto-approved, proceeding directly to "approved" state.

When a new harvest is added, a notification is sent to the user who created it. If a team is designated, team leaders are also notified. If a distributor is designated, distributor leaders are also notified.

Gleans are "closed" by team leaders or by a nightly background automated process on the server. Gleans with state "finished" are automatically closed after 30 days.

When a glean is closed, an email notification is sent to the user who created it. Team leaders are also notified.

Harvests are transferred to distributors.

Any signed-in user can create a transfer for a harvest.

A transfer typically transitions through these states: draft, pending, active, closed. After a transfer is created, it will be in "draft" state. If the transfer is created by a user designated as team or distributor leader, the transfer is auto-approved, proceeding directly to "active" state.

Only "active" transfers show on the website as opportunities for volunteers.

When a new transfer is added, a notification is sent to the user who created it. If a distributor is designated, distributor leaders are also notified. If a team is designated, team leaders are also notified.

A portioning is an event with the purpose of portioning the harvest into distributions.

Any signed-in user can create a portioning and submit it for approval by a distributor leader.

If the portioning is created by a user designated as team or distributor leader, the portioning is auto-approved, proceeding directly to "approved" state.

Only "approved" portionings show on the website as opportunities for volunteers.

When a new portioning is added, a notification is sent to the user who created it. If a distributor is designated, distributor leaders are also notified.

Distributions represent an event where free, portioned food is distributed. Distributions are assigned to a distribution site.

Any signed-in user can create a new distribution.

Distributions can be created from portionings, from harvests or on their own. Each distribution has a specified portion size and number of portions.

After a distribution is created, it will saved as a "draft". Any user can submit a distribution for approval by distributor leaders. If the distribution is created by a user designated as team or distributor leader, the distribution is auto-approved, proceeding directly to "approved" state.

Only "approved" distributions show on the website as opportunities for volunteers.

When a new distribution is added, a notification is sent to the user who created it. If a distributor is designated, distributor leaders are also notified.

Harvests are automatically closed during portioning, as distributions are created from them.

When a portioning is closed, a notification is sent to the user who created it. If a distributor is designated, distributor leaders are also notified.

A portioning is closed when distributions have been created or when the event is cancelled.

Distributor leaders can close a portioning.

When a portioning is closed, a notification is sent to the user who created it. If a distributor is designated, distributor leaders are also notified.

Distributions are transferred to distributors.

Any signed-in user can create a transfer for a distribution.

A transfer typically transitions through these states: draft, pending, active, closed. After a transfer is created, it will be in "draft" state. If the transfer is created by a user designated as team or distributor leader, the transfer is auto-approved, proceeding directly to "active" state.

Only "active" transfers show on the website as opportunities for volunteers.

When a new transfer is added, a notification is sent to the user who created it. If a distributor is designated, distributor leaders are also notified. If a team is designated, team leaders are also notified.

Distributions are "started" by distribution leaders.

When a distribution is started, a notification is sent to the user who created it. Distributor leaders are also notified.

Distributions are "closed" by distribution leaders or by a nightly background automated process on the server. Distributions with state "finished" are automatically closed after 30 days.

When a distribution is closed, a notification is sent to the user who created it. Distributor leaders are also notified.