Casework

Residential permits

RLS, signed URLs and server-side privileged actions planned.

System controls

System settings

Operational configuration for routing, links, documents, approvals, exports and production readiness.

Admin changes are controlled for v1

These settings show the operating posture for staff review. Editable admin persistence should be enabled after staff authentication, role claims and server-side privileged actions are in place.

Environment

Production

Active

casework.egit.com.au

Database

Supabase

Active

RLS enabled with staff policies

Storage

Private buckets

Active

project-documents and generated-documents

Admin persistence

Not enabled

Planned

Settings remain controlled by config/code in v1

Branch routing

Queue ownership, branch spread and default staff assignment rules.

Active

OwnerOperations

Default routing

By municipality

Active

East Gippsland, Latrobe and Mount Alexander route to their configured branches.

Unassigned intake

Visible on dashboard

Active

Cases without an assessor remain in intake and are not hidden from queues.

Branch overrides

Admin only

Planned

Manual transfer will require administrator role and audit reason.

Secure links

Customer application and RFI invite defaults.

Planned

OwnerIntake

Invite expiry

15 days

Planned

Default expiry from environment setting for customer secure-link submissions.

Revocation

Staff action

Active

Revoked and expired RFI links already render separate applicant states.

Email delivery

Provider pending

Needs setup

Invite creation is modelled; outbound provider credentials are not connected yet.

Document and storage rules

Evidence storage, versioning and private document access controls.

Planned

OwnerSecurity

Project documents

Private bucket

Active

Supabase storage buckets are private and intended for signed server URLs.

Generated packages

Private bucket

Active

Export packages and generated documents stay separate from customer uploads.

Malware scanning

Pending provider

Needs setup

Schema tracks scan state; scanning service is not wired in v1 yet.

Decision guardrails

Human approval boundaries for assessment, RBS decisions and export release.

Active

OwnerCompliance

Assessor sign-off

Explicit

Active

Assessment revisions must be signed off by an assessor before RBS review.

RBS approval

Separate action

Active

PermAssist export is blocked until RBS approval is recorded.

Previous-stage changes

Fresh revision path

Active

Reopening earlier work creates a new path instead of mutating locked history.

PermAssist export

Package generation, mapping version and preflight rules.

Active

OwnerPermits

Mapping version

0.1

Active

Current adapter produces CSV package, manifest and validation report.

Preflight

Approval gated

Active

Export checks require project details, documents, sign-off and RBS approval.

Production import

PermAssist credentials

Needs setup

Direct submission/import credentials are not connected in this v1.

Integrations

External services used by the operational workflow.

Needs setup

OwnerPlatform

Supabase

Connected

Active

Database, RLS policies and storage buckets are configured.

Email provider

Mock provider

Needs setup

Outbound invite and RFI delivery needs provider credentials before staff launch.

Document analysis

Mock provider

Needs setup

Extraction scaffolding is present; production analysis provider is not selected.

Audit and retention

Evidence trail, actor attribution and retention posture.

Planned

OwnerAudit

Audit events

Application scoped

Active

Human decisions, generated packages and link actions are represented in the trail.

Actor snapshots

Role aware

Planned

Production events should persist actor id and role at the time of action.

Retention period

Policy pending

Needs setup

Council retention policy needs to be confirmed before enforcing archive rules.

Production readiness

What needs attention before staff rollout.

Core casework flow is active

Queues, revisions, RFIs, approval gates and export package generation are wired.

Provider setup remains

Email delivery, document analysis and production PermAssist credentials still need real provider configuration.

Editable settings come later

Settings mutations should wait for staff auth, role checks and audit-backed server actions.

Connected services

Current integration posture.

Supabase database

Connected

Active

Supabase storage

Private buckets

Active

Email delivery

Provider pending

Needs setup

Planning/title lookup

Provider pending

Needs setup

Readiness register

Operational items that drive whether a setting is active, planned or waiting on setup.

Area	State	Owner	Next action
Staff auth	Needs setup	Platform	Connect staff login and role claims
Outbound email	Needs setup	Platform	Configure invite and RFI provider
Secure storage	Active	Security	Issue signed URLs from server actions
PermAssist package	Active	Permits	Confirm import mapping with real PermAssist target
Audit retention	Planned	Audit	Confirm council retention period