Quickstart

The fastest way to understand d5s is to complete one real task in a chat. You do not need to configure a project, agent, or automation first.

New accounts choose a paid plan before the workspace opens; see Plans and credits. A Free organization from before 4 October 2026 can use the Light level immediately. Medium, High, and specific-model choices require a paid plan. An organization Owner or Admin can enable models allowed by the plan for its workspaces. If no model is available in the composer, ask an Owner or Admin to check Organization settings → Models, then contact d5s if an expected option is missing.

1. Start from the workspace home

New personal accounts begin with a seven-step welcome journey at Onboarding: welcome, team size, tool connections, your first agent, working context, invitations, and a completion review. The journey prepares a shared workspace that uses your first name, such as Taylor's team. Invite a colleague opens the shared workspace invitation form, including any seat review required for a colleague. The team size step also asks how you heard about d5s; that answer is optional. When you sign in with a verified work email, d5s reads your company website and pre-fills the working context step with a short draft. The step names the website it used. Edit or delete the draft before you continue; d5s never replaces text you typed. Personal email addresses, such as Gmail, get an empty field. Connections, context, and invitations are optional; Continue never authorizes a channel or sends an invitation by itself. From the tools step to the invitations step, Skip setup leaves the journey early: it keeps the answers you gave, creates your first agent, and opens workspace chat. Finishing the journey also opens workspace chat.

If you joined an existing workspace by invitation, open that workspace and start in chat. You do not need to create a personal workspace to join your team.

Otherwise, open your workspace and start a new chat. Describe the result you want, the relevant background, and any constraints. A useful opening request names the deliverable and the decision it should support, for example:

Review the attached customer notes, group the recurring objections, and create a short brief with the five issues we should address first. Show your evidence for each group.

If the work belongs to an existing project, choose it before sending. Otherwise, start directly; the chat keeps its files and results, and you can use Save as project later.

2. Add the right context

Attach files that are specific to this conversation. Put instructions or reference material that should affect future work in the project instead. This distinction prevents a one-off attachment from silently becoming standing context.

The composer also lets you choose the model, reasoning level, available tools, and approval mode. Connectors already configured in the workspace are available through the chat's project by default; turn off an unneeded connector from that project's connector settings. Keep the default Ask for approval mode when you want connector actions configured to Ask to pause. Choose Allow all only when you are comfortable letting those actions continue for the whole session without individual prompts. Explicit Deny rules and connector or network boundaries still apply.

3. Review the result

Follow progress in the conversation. A run can show tool calls, generated files, sub-agent work, research progress, and connector approval requests. In Ask mode, approve a requested connector action once (valid for 15 minutes and consumed by one call) or for the session (valid for up to 24 hours) only when the requested action is appropriate. Switching the conversation to Allow all does not create one of these approvals; it applies only while that session remains in Allow all mode.

Continue in the same chat while the goal is changing. A message you send during active work waits above the composer or joins the current work. For a waiting message, choose Steer to stop the current run and handle that message next, or × to delete it before it starts.

4. Keep what should last

Use Save as project when the chat has accumulated context you want to find and reuse. This keeps the chat and its files in place and lists them as a project.

Then choose a work mode: keep the conversation as a chat, staff an agent for an ongoing responsibility, create an automation for a defined job and trigger, or create a dashboard when the maintained output matters more than the transcript.