Nonprofits often manage volunteers, grant applicants, and sponsors in separate spreadsheets, inboxes, and form tools. Every new application creates more manual work: copying contact details, matching files to the right person, sending status updates, and answering questions that could have been handled through self-service.

Airtable can serve as the central database for all three workflows. miniExtensions adds the public forms and secure portals needed to let external users submit information, upload documents, check statuses, and update their own records without receiving access to the Airtable base.

The result is one operational system for your team and a separate, appropriate experience for every external audience.

What You Can Build

This setup can include:

  • A public volunteer application form
  • A volunteer portal for assignments, hours, forms, and resources
  • A public directory of available grant programs
  • A grant applicant portal for applications, decisions, and reports
  • A sponsorship inquiry or checkout form
  • A sponsor portal for payments, benefits, assets, and deliverables
  • Airtable views and automations for your internal team

For clearer permissions, use separate miniExtensions Portals for volunteers, grant applicants, and sponsors. Each group has its own user table, login experience, and related records.

Plan Your Airtable Base

Start by creating the tables that support each workflow. You can keep them in one Airtable base while maintaining clear links between contacts and their records.

For volunteer management, consider:

  • Volunteers
  • Volunteer Opportunities
  • Volunteer Applications
  • Shift Signups or Volunteer Assignments
  • Volunteer Hours
  • Volunteer Resources

For grant management, consider:

  • Grant Applicants
  • Grant Programs
  • Grant Applications
  • Grant Reports
  • Grant Documents

For sponsorship management, consider:

  • Sponsors
  • Sponsorship Packages
  • Sponsorships
  • Sponsor Deliverables
  • Payments

Each Portal-facing data table should contain a direct linked-record field back to its users table. For example, Shift Signups should have a Volunteer field linked to Volunteers, while Grant Applications should have an Applicant field linked to Grant Applicants.

This linked field is what miniExtensions uses to determine which records belong to the logged-in user.

Useful status fields might include:

  • Volunteer application: New, Reviewing, Approved, or Declined
  • Grant application: Draft, Submitted, Under Review, Accepted, or Not Selected
  • Sponsorship: Inquiry, Proposed, Awaiting Payment, Active, or Completed

Keep internal fields such as reviewer notes, risk assessments, budget approvals, and staff assignments separate from fields that external users should see.

Create a Public Volunteer Application Form

Create a Form extension in miniExtensions, select your Airtable base, and choose the Volunteer Applications table.

In the Form’s Fields section, add the information required from prospective volunteers, such as:

  • Name
  • Email address
  • Phone number
  • Location
  • Areas of interest
  • Availability
  • Relevant experience
  • Languages
  • Emergency contact
  • Volunteer opportunity
  • Resume or supporting files
  • Consent and acknowledgment

If applicants should choose an opportunity, add a linked-record field from Volunteer Applications to Volunteer Opportunities. Open that field’s settings and use Record Finder Options to control how opportunities are displayed and searched. You can filter records so that only published or active opportunities will be offered.

For waivers or acknowledgments, add a Signature field in miniExtensions and select the Airtable attachment field where the signature should be stored.

Leave internal fields such as Application Status, Reviewer, Screening Notes, and Background Check Status out of the public form. Set those values later through Airtable automations or your internal review process.

Configure the success message or redirect, then open the Share menu to copy the public link or embed the form on your nonprofit’s website.

Create the Volunteer Portal

Once a volunteer has been approved, give them access to a secure Portal where they can manage their participation.

Create a Portal extension and select the Airtable base. In the initial setup, select the first data table you want volunteers to see, such as Shift Signups or Volunteer Assignments. Then select that table’s Volunteer linked-record field, which points back to the Volunteers table.

In Users & Login, confirm the Volunteers table and configure the email field that volunteers will use to log in.

Under Tables, add the records volunteers should be able to access:

  • Volunteer applications
  • Shift signups or assignments
  • Volunteer hours
  • Training documents
  • Policies and resources
  • Certificates or acknowledgments

Configure the create form for Shift Signups with fields such as Opportunity, Shift, and Notes. There is no need to add the Volunteer field simply to establish ownership. When a volunteer creates the signup from inside the Portal, miniExtensions automatically links it to the logged-in volunteer.

Use the same approach for an hours form. Include fields such as Date, Assignment, Hours, and Activity Notes, but omit the Volunteer field. Again, the new hours record will be linked to the logged-in volunteer automatically.

In Profile, choose which personal fields volunteers can review or update. Hide internal fields throughout the Portal, then use the Share menu to distribute the login link.

The Portal automatically shows each volunteer the records linked to them through the selected user field. You do not need to create an additional filter that limits records to the logged-in user.

Publish Your Grant Opportunities

You can create a public grant directory before asking applicants to register or submit an application.

In Airtable, create an Open Grant Programs view containing only grants that are currently accepting applications. Include fields such as:

  • Program name
  • Summary
  • Eligibility
  • Available funding
  • Application deadline
  • Project period
  • Geographic restrictions
  • Application instructions
  • Cover image or supporting documents

Create an Interface extension in miniExtensions, select the Airtable base, and choose the Grant Programs table and the appropriate Airtable view. Configure the layout and visible fields, leaving internal budget notes, reviewers, and draft programs hidden.

Open Share when the directory is ready. You can publish its link directly or embed it on your website alongside an application button.

Create a Grant Application Form

For a public application process, create another Form extension, select the Airtable base, and choose Grant Applications.

Add the fields applicants need to complete, such as:

  • Organization name
  • Primary contact
  • Email and phone
  • Grant program
  • Project title
  • Project summary
  • Need statement
  • Intended outcomes
  • Amount requested
  • Project budget
  • Timeline
  • Supporting documents
  • Certification or signature

Configure the Grant Program linked-record field through Record Finder Options so applicants can find the relevant program. Where appropriate, limit the available choices to the Airtable view containing open programs.

Exclude fields such as Review Score, Reviewer, Internal Notes, Decision, and Approved Amount. Airtable automations can assign the initial status, record the submission date, notify your team, and send an acknowledgment to the applicant.

If applicants submit without logging in, use their email address to find or create a Grant Applicants record and link it to the application. If applications are created after applicants log into the grant Portal (see below), miniExtensions makes this user link automatically.

Create the Grant Applicant Portal

Create a separate Portal extension for grant applicants and select the Airtable base. Choose Grant Applications as the first data table, then select its Applicant field linking to Grant Applicants.

Under Tables, add the information applicants should be able to access:

  • Grant applications
  • Application decisions
  • Agreements
  • Grant reports
  • Required documents
  • Disbursement or payment records, if applicable

If applicants should start new applications from the Portal, enable record creation for Grant Applications. Include the program, narrative, budget, timeline, and attachment fields in the create form, but do not include Applicant. The application will automatically be linked to the logged-in applicant.

For reporting, configure Grant Reports as a related or child table under the appropriate grant application. Use the linked Grant Application field for that relationship. The report form might contain:

  • Reporting period
  • Progress summary
  • Outcome metrics
  • Challenges
  • Budget actuals
  • Supporting files
  • Next steps

Do not add the applicant field merely to establish ownership. Reports created inside the Portal are automatically associated with the logged-in applicant through the Portal’s user relationship.

Use read-only fields for decisions, approved amounts, deadlines, and staff feedback. Then test with two applicant accounts to confirm that each applicant sees only their own linked applications and reports.

Create a Sponsorship Inquiry Form

In Airtable, add sponsorship packages with fields such as package name, price, included benefits, event, availability, and description.

Create a Form extension in miniExtensions, select the Airtable base, and choose the Sponsorships or Sponsorship Requests table.

Add fields such as:

  • Organization name
  • Contact name
  • Email and phone
  • Sponsorship package
  • Event or campaign
  • Billing details
  • Logo upload
  • Website URL
  • Marketing preferences
  • Additional requests

Use the linked Sponsorship Package field’s Record Finder Options to control how packages appear. Limit the choices to currently available packages using an Airtable view when needed.

Hide internal fields such as Account Owner, Negotiated Amount, Fulfillment Notes, and Payment Status.

For an inquiry-only workflow, show a confirmation message and let your team follow up. If sponsors should pay immediately, add a Stripe checkout step.

Add Stripe Checkout for Sponsorship Payments

Configure the Stripe integration and add the required Airtable fields for the sponsorship record. These commonly include:

  • Payment amount
  • Payment status
  • Stripe payment or session ID
  • Receipt URL
  • Stripe checkout URL formula

Use the formula supplied by the integration to generate the checkout URL from the sponsorship record.

In the sponsorship Form settings, set the redirect URL after submission to the Airtable formula field containing the Stripe checkout URL. After submitting the sponsorship details, the sponsor is redirected to Stripe to complete payment.

Test the complete workflow using Stripe test keys before accepting live payments. Confirm that successful payments update the intended Airtable fields and that canceled or incomplete checkouts remain distinguishable from paid sponsorships.

Create the Sponsor Portal

Create another Portal extension and select the Airtable base. Choose Sponsorships as the first data table, then select its Sponsor linked-record field pointing to the Sponsors table.

Configure Users & Login using the sponsor email field. Under Tables, add:

  • Sponsorships
  • Packages and benefits
  • Payments and receipts
  • Sponsor deliverables
  • Uploaded logos and creative assets
  • Event information
  • Fulfillment status

Sponsors can use child forms to upload logos, advertisements, attendee lists, or other required materials. Include only the fields they need to complete and leave the Sponsor field out of the form. Records created inside the Portal are automatically linked to the logged-in sponsor.

Show payment status and receipt links as read-only fields. You can also expose benefit fulfillment fields so sponsors can see whether items such as signage, website placement, tickets, or speaking opportunities have been completed.

As with the other Portals, sponsors automatically see records linked to their account. No additional logged-in-user filter is required.

Automate the Internal Follow-Up in Airtable

Once the external experiences are working, add Airtable automations for recurring administrative tasks.

Useful automations include:

  • Notify staff when a volunteer application is submitted
  • Send an onboarding email when a volunteer is approved
  • Remind volunteers about upcoming assignments
  • Notify grant reviewers about new applications
  • Remind grantees before reporting deadlines
  • Send decision emails when a grant status changes
  • Alert sponsorship staff when a sponsor submits assets
  • Notify staff when payment is completed
  • Flag overdue sponsor deliverables

Create internal Airtable views such as New Volunteer Applications, Grants Awaiting Review, Reports Due This Month, Sponsors Awaiting Payment, and Missing Sponsor Assets. Your team can continue managing operations directly in Airtable while external users work through miniExtensions.

Protect Private Information

Keep public forms and directories limited to information intended for public access. Applications, payment records, internal reviews, contracts, and personal details should remain inside the relevant Portal.

Use separate Portals for volunteers, applicants, and sponsors instead of combining unrelated audiences into one login experience. Confirm that every Portal-facing data table has the correct direct link to its user table.

Review each table’s visible fields and child forms carefully. Internal notes, reviewer scores, private contact information, payment identifiers, and administrative fields should remain hidden unless there is a specific reason to expose them.

Test Every Workflow Before Launch

Test the system as each type of user:

  1. Submit a volunteer application and verify that all fields and attachments arrive in Airtable.
  2. Log in as two different volunteers and confirm that each sees only their own assignments and hours.
  3. Submit a grant application, upload supporting documents, and verify the initial status.
  4. Log in as two grant applicants and confirm that applications and reports remain separated.
  5. Submit a sponsorship request and complete a Stripe test checkout.
  6. Log in as two sponsors and confirm that each sees only their own sponsorships, payments, and deliverables.
  7. Create records from inside each Portal and verify that miniExtensions automatically links them to the logged-in user.
  8. Review every public page and Portal for accidentally exposed internal fields.

Run Your Nonprofit From One Airtable System

With Airtable and miniExtensions, nonprofits can replace disconnected forms, spreadsheets, and email threads with one coordinated system.

Volunteers receive a simple way to apply, manage assignments, and submit hours. Grant applicants can submit documents, monitor decisions, and complete reports. Sponsors can select packages, make payments, upload assets, and follow fulfillment progress.

Your staff retains Airtable as the central source of truth, while each external audience gets a focused experience containing only the records and actions relevant to them.