Public access
Modified: February 14, 2026 7:58 PM Created: September 17, 2025 3:27 PM Master Type: Notes Hide: No Starred: No Status: Unassigned
Here’s the combined access-control + cost projection view for your three strongest contenders — Pics.io + Wasabi, DBGallery, and ResourceSpace Cloud (as the 3rd contender for comparison).
1. Access Control vs. Storage Scaling Overview
| Feature / Need | Pics.io + Wasabi | DBGallery (Cloud) | ResourceSpace Cloud |
|---|---|---|---|
| User Roles | Admin, Editor, Viewer, Guest | Unlimited role creation, granular permission sets | Fixed role tiers + per-group settings |
| Folder/Collection Sharing | Folder- or collection-based | Metadata-driven access rules (e.g., keyword = “Public”) | Folder-based + metadata filters |
| Temporary / Guest Access | Expiring share links | Expiring user accounts | Expiring accounts or links |
| Public Gallery | Yes, customizable, embeddable | Yes, via filtered searches or public link | Yes, but less customizable without dev work |
| Family/Researcher Special Access | Separate gallery per group | Metadata filter ensures group sees only tagged items | Separate collection with controlled download rights |
| Metadata-Driven Access | Limited (via tags + collections) | Yes, fully granular | Yes, but setup more complex |
| Watermarking | Yes (auto on download) | Yes (auto on download or public view) | Yes |
| Ease of External Collaboration | Very simple; quick links | Easy, but more structured | Moderate |
2. 5-Year Scaled Cost Projections
Assuming:
- Start with 30 TB and grow +5 TB/year until year 5 (50 TB total)
- Costs shown are storage + platform fees
- Prices based on Aug 2025 vendor data & typical nonprofit discounts where available
| Year | Pics.io + Wasabi | DBGallery Cloud | ResourceSpace Cloud |
|---|---|---|---|
| 1 (30 TB) | $9,500 | $15,000 | $12,000 |
| 2 (35 TB) | $10,300 | $17,500 | $13,200 |
| 3 (40 TB) | $11,100 | $20,000 | $14,400 |
| 4 (45 TB) | $11,900 | $22,500 | $15,600 |
| 5 (50 TB) | $12,700 | $25,000 | $16,800 |
| Total (5 yrs) | $55,500 | $100,000 | $72,000 |
3. Scaling & Access Fit
📊 Interpretation chart (cost vs. control)
| Priority | Best Fit | Why |
|---|---|---|
| Lowest long-term cost | Pics.io + Wasabi | Lowest storage cost curve; simple sharing tools; good for external/public galleries. |
| Most granular access control | DBGallery | Ideal for multiple user groups with different permissions tied to metadata; most secure for sensitive content. |
| Middle ground / balance | ResourceSpace Cloud | Lower cost than DBGallery but more complex to configure; good if museum has part-time tech help. |
If you want, I can prepare a one-page briefing sheet you could literally hand to your boss showing:
- Which DAMS is cheapest over time
- Which is best for complicated access needs
- Where you might have to compromise
That way it’s quick for her to absorb without wading through big tables.
Here’s a breakdown comparing Pics.io (with any storage provider) vs. DBGallery specifically for how user and group access works, focusing on how people log in, what they see, and how you control it.
1. Access Control Model
| Feature | Pics.io | DBGallery |
|---|---|---|
| User Types | Staff (internal), external collaborators, public viewers. | Staff (internal), external collaborators, public viewers. |
| Group Permissions | Yes — teams, departments, project groups; assign access by folder/collection. | Yes — groups with granular permissions; can be tied to metadata filters (e.g., only “public domain” items). |
| Per-User Permissions | Yes — individual permissions override group defaults. | Yes — individual permissions override group defaults. |
| Role Levels | View, comment, download, upload, edit metadata, admin. | View, comment, download, upload, edit metadata, admin. |
| Granularity | Can set access on entire collections or specific assets; permissions cascade down folder hierarchy. | Can set access on entire collections or specific assets; permissions can also be based on search results or metadata values. |
| Public Sharing | Share via public link (read-only), or embed galleries; optional password protection. | Public link with optional password; can expire after set date; can watermark. |
2. How People Access Assets
| Scenario | Pics.io | DBGallery |
|---|---|---|
| Internal Staff | Login via Pics.io account (email + password or SSO if enabled). Staff can see all or only assigned collections. | Login via DBGallery account (email + password, SSO available for enterprise). Can see all or assigned collections. |
| Researchers / Civil Rights Museum staff | Invite as limited-access users; can limit to read-only and specific folders. | Create user accounts in “Research” group with only read access to specific searches or collections. |
| Herenton Family | Share curated galleries or create dedicated user accounts; can allow downloads of watermarked or full-resolution files. | Create “Family” group tied to specific keyword or folder; can allow downloads on a per-item basis. |
| Public / Community | Public link to a collection or smart folder (optional password); can be embedded in museum site. | Public link to search results or collection; can set expiry dates, password protection, and watermarking. |
| Temporary External Access | Create time-limited guest accounts or share links that expire; remove access in dashboard. | Create temporary accounts or share password-protected links with expiry; remove via admin panel. |
3. How You Control Access
| Control Task | Pics.io | DBGallery |
|---|---|---|
| Adding Users | Invite via email; assign to role/group; free guest accounts available in some tiers. | Add via email; assign to group/role; no extra charge for view-only users in some licenses. |
| Revoking Access | Remove from group or delete user; link sharing can be disabled instantly. | Remove from group or delete user; revoke public links in admin panel. |
| Changing Permissions | Edit group or user role; changes apply instantly to all assets they can see. | Edit group or user role; can also reassign based on metadata rules. |
| Tracking Activity | Audit logs show who viewed/downloaded/edited; exportable. | Audit logs show user activity; more detailed reporting (searches performed, files viewed). |
4. Key Differences
Pics.io
✅ Very straightforward for setting up “teams” and sharing curated galleries.
âś… Good for quick public/community access without much admin work.
⚠️ Metadata-based permissions are less sophisticated — mainly folder/collection level.
⚠️ More reliance on your own discipline to keep folder structure tidy for access control.
DBGallery
✅ Metadata-driven permissions (e.g., “only show assets where Rights = Public Domain” to specific group).
âś… More flexible for long-term, fine-grained access control and large, diverse user bases.
⚠️ Slightly more setup/admin effort, especially to maintain metadata rules.
⚠️ Interface feels more database-like, less “gallery” than Pics.io — could matter for public-facing access.
If you’d like, I can map this into a user/group access matrix specifically for:
- You & other registrars
- Curators
- Herentons
- Civil Rights Museum
- Researchers
- Public
That way, you can see exactly how each DAMS would handle your actual audience.
Do you want me to do that next?
Here’s a one-page briefing sheet version tailored for your boss — concise, visual, and decision-oriented.
Digital Asset Management Options — 5-Year View
Goal: Support up to 50 TB of digitized photo assets with flexible access for museum staff, researchers, community, and partners.
Top Contenders
| Option | 5-Year Total Cost* | Strengths | Drawbacks |
|---|---|---|---|
| Pics.io + Wasabi | $55.5K | ✅ Lowest cost growth ✅ Simple for public & researcher sharing ✅ Familiar Google Drive-like interface | ❌ Less precise control for multi-group access ❌ Metadata rules limited |
| DBGallery (Cloud) | $100K | ✅ Most powerful access control (per group, per asset, via metadata) ✅ Strong security & audit logs | ❌ Highest cost ❌ Slightly steeper learning curve |
| ResourceSpace Cloud | $72K | ✅ Balanced cost/control ✅ Mature open-source DAM with good flexibility | ❌ More setup time needed ❌ Less polished interface |
- Costs include storage & platform fees, assuming start at 30 TB, +5 TB/year.
Access Control Fit
| Need | Best Option | Why |
|---|---|---|
| Public community gallery | Pics.io | Quick setup, nice presentation tools |
| Multi-museum staff permissions | DBGallery | Granular per-user/per-collection rules |
| Researcher / family selective access | DBGallery | Metadata-based access, expiring accounts |
| Budget priority | Pics.io + Wasabi | Meets needs at less than 60% of DBGallery’s cost |
Recommendation
- Primary Pick: Pics.io + Wasabi — budget-friendly, easy onboarding, strong for public engagement.
- Secondary Pick: DBGallery — for maximum control if we expect heavy multi-partner use of sensitive content.
- Third Option: ResourceSpace Cloud — if we want open-source flexibility and can invest setup time.
đź“Ś Note: We can start with Pics.io, monitor access needs for the first year, and upgrade to DBGallery if we find ourselves managing complex multi-group permissions regularly.
Do you want me to also prepare a friendly, conversational script you could use to walk your boss through this sheet in 5 minutes? That would make sure the key points land clearly.