Admin CRUD Readiness Review

Purpose

This review separates non-personal configuration metadata that may be safe to design later from identity, submission, staff-decision, and tracking areas that must remain blocked.

It is readiness-only. It does not add CRUD, migrations, write endpoints, user assignment, workflow activation, or storage.

Why CRUD Readiness Comes Before CRUD

Admin configuration can affect community permissions, workflow behavior, retention, and public display. Renata needs a decision framework before any configuration area becomes editable, even if the first future target is only low-sensitivity template metadata.

The readiness rule is simple: if it touches people, submissions, staff decisions, exports, identity, retention behavior, or tracking, it stays blocked.

Candidate Admin Areas

Area	Category	Proposed CRUD status	Data sensitivity	Why it matters
Role Set Templates role-set-templates	safe-first config	candidate-config-only	low configuration sensitivity	Role templates are non-personal configuration metadata for future deployments.
Workflow Set Templates workflow-set-templates	safe-first config	candidate-config-only	low configuration sensitivity	Workflow templates can describe enabled modules and review gates without collecting submissions.
Community Display Settings community-display-settings	safe-first config	candidate-config-only	low configuration sensitivity	Display labels and instance copy can support productization without storing people or sensitive content.
Retention Policy Templates retention-policy-templates	policy template metadata	requires-privacy-approval	policy-sensitive configuration	Retention settings affect how future records may be kept or removed.
Review Policy Templates review-policy-templates	policy template metadata	requires-staff-approval	policy-sensitive configuration	Review policy controls future staff gates and public display boundaries.
User Admin user-admin	identity-adjacent	blocked	identity-sensitive	User admin would involve people, access, and identity policy.
Role Assignment role-assignment	identity-adjacent	blocked	identity-sensitive	Role assignment grants access and future workflow authority.
Live Submission Management live-submission-management	sensitive workflow	blocked	high community-content sensitivity	Live pull-up and push-up content may contain sensitive community information.
Staff Review Decisions staff-review-decisions	sensitive workflow	blocked	high review sensitivity	Staff decisions affect what may become public and what must be retained or removed.
Morning Sheet Placement morning-sheet-placement	public display workflow	blocked	public-display sensitive	Live placement would expose reviewed community content to a meeting surface.
Export Management export-management	data access	blocked	high data-access sensitivity	Exports can copy sensitive records outside the app boundary.
AI Policy Management ai-policy-management	AI governance	requires-privacy-approval	AI governance sensitivity	Any AI use for real community submissions would require a separate approval path.
Attendance Tracking attendance-tracking	never track	never	restricted tracking data	Attendance tracking is outside the product boundary.
Participation Tracking participation-tracking	never track	never	restricted tracking data	Participation tracking would turn accountability into surveillance.
Participation Analytics participation-analytics	never track	never	restricted analytics data	Participation analytics is an explicit no-tracking product boundary.
Scoring / Ranking / Compliance Metrics scoring-ranking-compliance-metrics	never track	never	restricted evaluative data	Scoring, ranking, discipline points, and compliance metrics are outside Renata boundaries.

Safe-First Config-Only Candidates

Role Set Templates

A later planning-only design may define how template labels, role keys, and permission presets could be edited without users or assignments.

Required gates: D1 schema review, audit logging design, rollback plan, staff/privacy approval

Exclusions: no user assignment; no identity storage; no permission activation; no live role CRUD in this phase

candidate-config-only

Workflow Set Templates

A later design may cover template metadata only, with no module activation and no live workflow behavior.

Required gates: D1 schema review, audit logging design, rollback plan, staff/privacy approval

Exclusions: no workflow activation; no submissions; no staff decisions; no live workflow CRUD in this phase

candidate-config-only

Community Display Settings

A later design may define non-sensitive display labels only; no real customer roster or facility details.

Required gates: D1 schema review, audit logging design, rollback plan

Exclusions: no real customer list; no resident data; no staff roster; no facility-sensitive details

candidate-config-only

These are possible future config-only candidates, not active features. They still require audit logging, D1 schema review, rollback planning, and staff/privacy approval where needed.

Blocked Admin Areas

User Admin

Remain preview-only until identity and privacy decisions are complete.

Required gates: identity policy, privacy approval, account model approval, audit logging design

Exclusions: no live user CRUD; no account creation; no profiles; no email storage

blocked

Role Assignment

Remain blocked until real roles, people, and approval boundaries are approved.

Required gates: identity policy, staff approval, privacy approval, audit logging design

Exclusions: no live role assignment; no permission activation; no reviewer designation; no user records

blocked

Live Submission Management

Remain blocked until the full protected workflow, storage, review, and retention model is approved.

Required gates: staff approval, privacy approval, retention policy, audit logging design

Exclusions: no submission collection; no draft storage; no sensitive community content; no resident content

blocked

Staff Review Decisions

Remain blocked until decision authority, logging, and retention rules are approved.

Required gates: staff approval, privacy approval, audit logging design, retention policy

Exclusions: no approve actions; no reject actions; no staff decisions; no review event writes

blocked

Morning Sheet Placement

Remain synthetic until public-display approval and removal rules exist.

Required gates: staff approval, privacy approval, audit logging design, rollback plan

Exclusions: no real Morning Sheet placement; no public display of submissions; no placement writes

blocked

Export Management

Remain blocked until the data model and export policy are reviewed.

Required gates: staff approval, privacy approval, export policy, audit logging design

Exclusions: no exports; no downloadable records; no bulk access; no reporting extracts

blocked

Attendance Tracking

Do not design CRUD for this area.

Required gates: explicit separate policy would be required outside this roadmap

Exclusions: no attendance tracking; no attendance records; no attendance dashboards

never

Participation Tracking

Do not design CRUD for this area.

Required gates: explicit separate policy would be required outside this roadmap

Exclusions: no participation tracking; no participation records; no participation dashboards

never

Participation Analytics

Do not design CRUD for this area.

Required gates: explicit separate policy would be required outside this roadmap

Exclusions: no participation analytics; no resident performance dashboards; no behavioral analytics

never

Scoring / Ranking / Compliance Metrics

Do not design CRUD for this area.

Required gates: explicit separate policy would be required outside this roadmap

Exclusions: no scoring; no ranking; no discipline points; no compliance metrics

never

Required Technical Gates

D1 schema reviewed before any storage design moves forward.
Audit logging designed before any configuration changes are allowed.
Rollback plan documented before a pilot can change configuration.
No migration, write endpoint, or runtime configuration change exists in this phase.

Required Privacy/Staff Gates

D1 schema reviewaudit logging designrollback planstaff/privacy approvalconfiguration change reviewno resident identity storageno submission storageno staff decision workflow

First Recommended Live CRUD Candidate

Phase 7.5 - Config-Only Role Set CRUD Design, Planning Only

Design only the narrowest future CRUD path for non-personal role-set template metadata.

Candidate: role-set-templates

not implementation yetno migrations yetno writes yetno user assignmentno identity captureno submissions

What Must Never Become CRUD

attendance tracking participation tracking participation analytics scoring/ranking/compliance metrics resident performance dashboards discipline points

What Remains Blocked

no live CRUDno active migrationsno database writesno account creationno identity storageno user assignmentno role assignmentno workflow activationno submission collectionno staff decisionsno attendance trackingno participation trackingno participation analyticsno scoring/ranking/compliance metrics

Recommended Next Phase

Phase 7.6 - Role Set Template Schema Planning

Phase 7.5 now adds the role-set CRUD design preview. The next planning step is schema planning only, without active migrations, writes, user assignment, identity capture, or submissions.

Safe-first candidate IDs: role-set-templates, workflow-set-templates, community-display-settings

planning-only