Settings and notifications

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

Account settings

Open your profile menu to manage:

• name and profile information;
• authentication and active sessions;
• appearance and theme;
• default timezone;
• notification delivery;
• installed desktop and mobile devices;
• 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;
• notification policies;
• 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 and Codex settings

Choose which supported providers are available to the workspace. For Codex, connect through OpenAI browser sign-in for subscription access or use an API key for usage-based access.

Provider availability, models, and limits can change according to the external provider and your plan. A default model is a preference, not a guarantee that every to-do will use the same model; Doozy can select a compatible model or fail over according to workspace policy.

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

Configure in-app, email, desktop, and mobile notifications by event. A useful default is to notify for approvals, direct mentions, failures, and to-dos that need input, while keeping scheduled success in the activity feed.

You can override notifications for a high-priority workspace or Doozy. Muting a notification doesn’t pause the underlying schedule (aka routine or timed automation).

Usage and billing

The usage view separates Doozy plan usage from externally billed provider usage when possible. Subscription-backed Codex work doesn’t add a separate Doozy model-usage charge, but your Doozy plan and included minutes still apply. OpenAI controls subscription limits and API-key charges; connected apps may also have their own quotas or fees.

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