Most platforms claim to be configurable, but when you actually need to change something, you're told to file a ticket or hire a developer. Zeph's admin panel puts every configurable aspect of the platform into a single, organized interface — no code changes, no support tickets, no waiting. Over 60 tabs of settings, each one designed to be changed by your team, on your schedule.
What Can You Configure?
The admin panel is organized into logical sections that cover every operational dimension of the platform. Here's a walk through the major configuration areas and what they let you control.
Terminology & Labels — Every field label, button text, status name, and column header in the platform can be renamed to match your organization's language. If your office calls cases "incidents," referrals "intakes," or complaints "grievances," the platform adapts to you — not the other way around. This isn't a cosmetic feature. It eliminates the cognitive overhead of translating between what the software says and what your team actually calls things, which directly reduces training time and data entry errors.
Case Types & Workflows — Define as many case types as your organization needs, each with its own lifecycle stages, required fields per stage, and auto-assignment rules. A death investigation case can have completely different workflow stages than a FOIA request or a complaint review. The system enforces required fields at each stage transition, so cases can't advance until the necessary information is captured. Auto-assignment rules route new cases to the right team member based on case type, jurisdiction, workload, or any custom criteria you define.
Security & Access Control — The RBAC permission matrix lets you define exactly who can see, edit, create, and delete records at the module, submodule, and tab level. Security groups bundle permissions into reusable roles — "Investigator," "Supervisor," "Read-Only Auditor," "Portal Admin" — and users can belong to multiple groups. When a new module is enabled or a new tab is added, you control who gets access from day one. There's no default-open model where you have to retroactively lock things down.
Portal & Branding — The public-facing portal is fully configurable from the admin panel. Upload your organization's logo, set the color scheme, configure which search fields are available to the public, control what information is disclosed in search results, and customize the request submission forms. You can enable or disable entire portal features — public case search, document requests, FOIA submissions — without any code changes. The portal reflects your brand, not ours.
Notifications & Alerts — Configure email templates for every automated notification the system sends. Set up escalation rules that trigger when deadlines are approaching or SLA thresholds are breached. Define alert recipients by role, by case type, or by specific assignment. Every notification template supports dynamic placeholders for case numbers, dates, names, and statuses — so your automated emails read like they were written by your team, not generated by software.
Reporting — Set up scheduled reports that run daily, weekly, or monthly and deliver results to specific email addresses or dashboard views. Define ad-hoc report templates that your team can run on demand with customizable filters and date ranges. Configure export formats — PDF, CSV, Excel — and control which fields are included in each report type. Reporting configuration is role-aware, so different user groups can have access to different report templates.
Why This Matters
Traditional enterprise software charges for professional services to make configuration changes. Need to add a new case type? That's a statement of work. Want to rename a field? Submit a change request and wait for the next release cycle. This model is slow, expensive, and it creates a dependency on the vendor for routine operational decisions.
In Zeph, your admin can make changes in real time. Add a new case type on Monday, adjust the workflow on Wednesday, update the notification templates on Friday — all without filing a single support ticket. This means faster onboarding for new staff, lower total cost of ownership over the life of the contract, and the ability to iterate on workflows as your operations evolve. Your platform grows with your organization instead of holding it back.
Multi-Tenant Aware
Every configuration in the admin panel is per-entity. If your deployment serves multiple offices, departments, or jurisdictions, each entity can have its own terminology, case types, workflow stages, branding, and security groups — all within the same installation. A county medical examiner's office and a coroner's office can share the same platform while maintaining completely independent configurations, workflows, and data boundaries.
This multi-tenant architecture is built into the configuration layer itself. When an admin logs in, they see only the configuration for their entity. There's no risk of one office's changes affecting another. And system-wide administrators can view and manage all entities from a single dashboard, making centralized oversight straightforward without sacrificing local autonomy.
No Upgrade Conflicts
Because configurations are stored separately from application code, software updates apply cleanly. When a new version of the platform is released, your customizations — terminology overrides, workflow definitions, permission structures, portal branding — are never overwritten. The update process applies database migrations and code changes without touching configuration data. This means you can stay current on security patches and feature releases without the fear that an upgrade will undo months of careful configuration work.
This separation also makes it straightforward to test upgrades. You can review what's changing in the release notes, apply the update, and verify that your configurations are intact — all without a lengthy regression testing cycle or vendor-assisted upgrade process.