Settings and notifications

Settings exist at the account, workspace, and Doozy levels. Check the scope before changing a provider, connection, or permission.

Account settings

Open your profile menu to manage:

• name and profile information;
• authentication and active sessions;
• appearance and theme;
• default timezone;
• scheduled-task email and text notifications;
• account deletion and data requests.

Use a timezone that matches how you interpret schedules. Individual workspaces can override it when a team operates elsewhere.

Workspace settings

Workspace owners and admins can manage:

• workspace name and timezone;
• members and roles;
• connected apps and toolkits;
• model providers, including Codex;
• the Morph environment;
• approval defaults;
• billing and usage;
• retention, export, and deletion.

Connections and Morph credentials are workspace-scoped. Changing them can affect several Doozies and active schedules at once.

Model, Codex, and BYO key settings

Free is bring your own AI. Connect Codex through OpenAI browser sign-in, or securely save OpenRouter, Deepgram, and Composio keys for server-side work. Those providers bill you directly.

Runs authenticated with your provider keys consume zero Doozy minutes and work from web or mobile while your devices are closed. Codex subscription runs still use the desktop connector.

Never paste provider credentials into a Doozy job description, memory, skill, or conversation.

Morph settings

The Morph panel shows environment status, storage, region, recent recovery operations, and access controls. Workspace admins can update the environment, restart services, recover durable state, or reset to a snapshot.

A reset can discard recent unsynchronized work. Commit repositories and preserve important artifacts before resetting.

Edit one Doozy

Open Doozies, select a Doozy, and choose Edit to change its:

• job description and attached files;
• responsibilities and schedules;
• skills (aka playbooks, procedures, or prompt templates);
• toolkit (aka plugin or tool set) and connections (aka connectors or integrations);
• working hours (aka availability window);
• approval classifier;
• profile image and display name;
• active or archived state.

Use direct conversation guidance when a change must affect work already in progress.

Approval defaults

Approval rules can be set at the workspace and Doozy levels. The more restrictive applicable rule wins. A Doozy can’t weaken a workspace policy through its own job description.

Keep always-allow rules narrow: identify the tool, action, target, and conditions. Review them after a connection changes scope.

Understand attention states

Doozy separates ordinary progress from items that need you. Common states include:

• Working: execution is active and no input is required.
• Needs input: the Doozy can’t safely resolve a material choice.
• Approval required: a proposed action is waiting for review.
• Completed: the requested result is ready.
• Failed: work stopped and includes an error or recovery path.

The To-dos list (aka task queue or project list) and Conversations filters let you focus on blocked or consequential work instead of watching every run.

Control notifications

Catch Up on the To-dos page is the one place to review what needs you: approvals, questions, failures, and new results. Open an item to jump to the exact message, then mark it checked or snooze it.

Under Settings > Notifications, turn scheduled-task email and text messages on or off. Email covers approvals and failures from scheduled to-dos (aka routines or timed automations), plus the daily catch-up digest.

Usage and billing

The usage view separates Doozy minutes from transcription minutes. On Free, hosted allowances are zero and BYO usage is billed by your provider. Paid plans include monthly Doozy-hosted execution minutes and separate transcription minutes.

Set workspace budgets and review unusual increases. Parallel Doozies, browser sessions, long-running to-dos, and large context can consume more resources than a short conversation.

Updates and beta features

Desktop and mobile apps notify you when updates are available. Web updates arrive automatically. Workspace admins can control beta features for the team when a feature changes data access, execution, or governance.

Frequently Asked Questions