How SNAP helps rental car companies and shuttle operators accomplish scalable operations using multi-tenant organization and site management.
Introduction
Rental car companies, shuttle operators, and parking managers often run multiple locations. Each location may have multiple cameras and users. SNAP’s multi-tenant architecture lets you organize by organization and site: each org has one or more sites, each site has one or more cameras, and users are assigned to orgs with role-based access.
Org admins manage their organization—sites, cameras, users, billing. Sys admins manage the entire platform—organizations, retention, and system-wide settings. Users see only their org’s sites and snap data. The hierarchy keeps data isolated and operations manageable as you scale.
This guide covers the org/site hierarchy, roles, permissions, and best practices for managing multi-site operations.
Why This Feature Matters — Scalability and Isolation
- Scalability: Add sites and cameras without restructuring; the hierarchy scales.
- Isolation: Each org’s data is isolated; users see only their org.
- Role-based access: Org admins manage their org; sys admins manage the platform.
- Flexibility: Support franchise models, multi-brand, or single-org deployments.
- Billing: Billing can be configured per org, per site, or per camera.
What You Get When You Use This Feature
Your Workflow
- Create organization: Sys admin creates org; org admin can be assigned.
- Add sites: Org admin adds sites under the org (e.g., Downtown Lot, Airport, etc.).
- Add cameras: Assign cameras to sites; each camera belongs to one site.
- Add users: Invite users to the org; assign roles (User, Org Admin).
- Configure: Set retention, billing, and org-level settings.
What the Feature Produces
- Hierarchy: Org → Sites → Cameras; Users → Org.
- Access control: Users see only their org’s sites and snaps.
- Scoped reports: Report search and daily reports are scoped to org (or system for sys admin).
Understanding the Results
Hierarchy
| Level | Description |
|---|---|
| Organization | Top-level tenant; has sites, users, retention, billing |
| Site | Location within an org; has cameras |
| Camera | Belongs to one site; captures images |
| User | Belongs to one org; has role (User, OrgAdmin, SysAdmin) |
Roles
| Role | Scope |
|---|---|
| User | Own snaps; org’s sites and cameras |
| Org Admin | Full org management: sites, cameras, users, billing |
| Sys Admin | Platform-wide: orgs, retention, system settings |
Reports and Deliverables
- Org admin views: Org settings, site list, camera list, user list.
- Sys admin views: Organization list, org details, retention, billing summary.
- Scoped reports: Report search and daily reports respect org scope.
Best Practices
- Name sites clearly: Use consistent naming (e.g., “Airport – Lot A”) for easy filtering in reports.
- Assign org admins early: Org admins can manage their org; sys admins don’t need to handle day-to-day config.
- Use sites for physical locations: Group cameras by physical location for logical report filtering.
- Review user access: Periodically audit users and roles to ensure correct access.
- Set org timezone: Daily reports use org timezone; ensure it’s correct for each org.
Conclusion
SNAP’s multi-tenant site management keeps your operations organized as you scale. Org → Site → Camera hierarchy, role-based access, and scoped reports give you structure without complexity. Explore Admin > Organization and Sys Admin > Organizations to manage your setup.
The post Multi-Tenant Site Management: A Complete Guide to Organizing Your Operations first appeared on C2IT Labs.