Administration guide
Use your organization’s application address and a staff account. Superusers manage installation-wide configuration; department and organization administrators coordinate work within their permitted scope. A Community contributor account does not grant staff access.
Directory and location tasks
Section titled “Directory and location tasks”| Task | Guide |
|---|---|
| Bilingual labels, Community subcategories, routing and retirement | Categories and subcategories |
| Handling teams, contact details and VZD department leads | Organizations and departments |
| Staff roles, memberships, invitations, reset links and deactivation | People, users and invitations |
| VZD maps/plans, area drawing, microlocations and QR lifecycle | Areas, plans and QR locations |
Configuration and oversight
Section titled “Configuration and oversight”| Task | Guide |
|---|---|
| Bell notifications, event routing, audiences and deadline channels | Notifications and rules |
| Bilingual message content, variables and preview | Email templates |
| Community transition matrix and named VZD director | Workflow permissions and leadership |
| Branding, privacy, intake, maps, funding and saved SMTP settings | Appearance, privacy and mail settings |
| Charts, consent-based analytics, contributor counts and exports | Analytics, statistics and exports |
| Evaluation, licence requests, imports, renewal and expiry | Licensing and evaluation |
For server installation, use the Docker quickstart. For SMTP credentials, S3 and other runtime variables, use the environment reference.
Check access before changing configuration
Section titled “Check access before changing configuration”Check the header’s selected organization, active membership, role and case assignment. “All organizations” means your eligible scope. A performed VZD action may be locked pending review; a Community report may still need confirmation or publication approval. Read-only licence access is explained in the licensing guide.
For ordinary case work, use Community handling or VZD case management. Contact your instance administrator for access problems. For product support, provide module, version, screen, steps and error; redact credentials, private evidence and QR/access tokens.