Hello everyone,
I have been developing on AppSheet since 2016 to manage resources and activities for an environmental volunteer group supporting wildlife conservation.
My application has grown significantly and handles several distinct workflows using Security Filters and User Roles to ensure strict data privacy. I am looking for advice on how to optimize its architecture or restructure our user management as our team expands.
Here is a summary of the current setup:
- Patrol & Incident Logging: A multi-tab form capturing general timekeeping, mileage, a conservation checklist, photo uploads, and GPS logging for a patrol group.
- Intelligence Reports: A secure form capturing informant/suspect data and suspicious vehicle sightings. Accessible only to the creator and the committee via User Roles.
- Membership Management: Tracks internal member profiles and photos, restricted via Security Filters so individuals can only view/edit their own data. Allows for online joining application forms.
- Individual Timesheets: Separate logs for individual hours, ensuring individual tracking even when group patrol logs are submitted.
- Asset Register & Wildlife Sightings: Tracks group assets (restricted access) and logs rare animal/bird sightings with GPS coordinates for wildlife monitoring.
The Current Challenge:
Because we rely heavily on user-specific views and data privacy boundaries, the app is configured as a secure application. As our volunteer numbers have increased, we have run into account scaling limits and app freezes.
Since we are a registered environmental NPO with a zero-dollar budget, I would love to hear from the community:
- Have other non-profits successfully integrated AppSheet with the Google for Nonprofits program?
- Are there any architectural tips to safely handle user-restricted data (like our intelligence reports) without hitting individual user license walls, or is a dedicated NPO license plan the only viable path?
Any insights from fellow developers would be highly appreciated!