DALO OS/System/Settings
Settings
System configuration & preferences.
Drop work New task
Thu, 30 Apr, 09:33 pm
Local worker offline — bot chat will queue jobs but not complete until the worker is running.
No worker has registered yet. Start one with cd worker && npm start.
0 queued0 running0 failed

Users & roles

Founder + team + viewer roles.
NameEmailRoleFounderPrivate assistant
Josh Whitelawjosh@nothoughts.aufounderYesCesc
Chris Wilsonchris@nothoughts.aufounderYesBorgy

Integrations

Connected

Execution mode

Local worker handles all bot execution via Claude Code. Provider: claude-code.
Not configured

Supabase

Not configured. Set NEXT_PUBLIC_SUPABASE_URL + keys in .env.local.
Not configured

n8n

Set N8N_WEBHOOK_BASE_URL + per-workflow webhook env keys.

Visibility scopes

Founder Assistant Access Rules.
  • Cesc is Josh-only. Borgy is Chris-only.
  • Private assistant chats, notes, reminders never cross between founders.
  • Business-visible outputs from either assistant route into DALO OS shared surfaces after the founder approves visibility.
  • RLS on assistant_messages enforces owner-only reads.

Security posture

DALO OS does not store credentials. The account registry holds platform IDs and metadata only. 2FA challenges escalate to a human. Approval is required for every outbound send, publish, spend, or live-system change. See SECURITY_NOTES.md in the repo root.

DALO OS — Workforce Command Centre