Operations

Admin and security

Last updated 2026-07-30T20:30:47+00:00

Racinage separates family-user permissions from platform administration. Keep permissions narrow and review public sharing settings before exposing family data.

Family user permissions

Family managers should grant only the permissions a user needs. Tree editing, public sharing, person updates, finance records, and document access should be treated as separate responsibilities.

• Give editing permissions to trusted family maintainers.
• Give view-only access to users who only need to browse records.
• Review user access after major family events or role changes.

Super-admin area

The super-admin area is served separately from admin7839/. It is intended for platform operations such as managing family accounts, system settings, maintenance mode, and support details.

Private data

Family data can include living people, children, phone numbers, locations, financial records, documents, and private history. Treat public share links and exported files as sensitive.

Two-factor authentication

Users and super admins can enable an authenticator app from their Account page after verifying their email address. Save the ten one-time backup codes away from the device. A verified-email recovery can reset the authenticator after the password is checked, and signs out other sessions as a security precaution.

Account deletion and recovery

Requesting account deletion requires the current password and, when enabled, an authenticator or backup code. Unresolved payments, payouts, refunds, and reviews must be completed first. The account is locked immediately for exactly seven days.

• Signing in with valid credentials opens the restricted pending-deletion page, not the normal dashboard.
• The account holder can download a complete account archive, restore the account, and decide what happens to each shared resource.
• A shared resource transfers only after its current owner explicitly approves an eligible collaborator.
• If a shared resource is still unresolved, the whole deadline extends by another seven days.
• Restoration does not reverse completed ownership transfers or reactivate renewals and revoked device connections.

Messaging safety

Direct messages begin with a one-time username request. Private groups require accepted invitations, and resource chats follow active collaboration access. Users can report an exact message, voice recording, or attachment. Messaging moderators see only that reported item and minimized metadata, never ordinary conversation content. Warnings, item removal, timed messaging suspension, and permanent messaging bans are separate from whole-account suspension.

Deployment safety

Production deployment is handled by the repository workflow. Do not commit real secrets or private uploads. The workflow excludes config.php, database dumps, private user media, and other runtime data.

git status
git add docs
git commit -m "Add documentation site"
git push origin main

Database changes

When a schema change is needed, apply it intentionally and record the SQL. Performance indexes for large trees should exist on the relationship tables so tree reads do not scan unnecessary rows.