Workspaces

A workspace is the day-to-day operating boundary in d5s. It contains projects, chats, agents, automations, dashboards, and the capability catalogs those resources can use.

Every workspace belongs to an organization, and an organization can contain multiple workspaces. The organization is the broader administrative boundary for people, invitations, groups, billing, entitlements, usage, and audit history.

An organization has one selected d5s region, and its workspaces use that same region. One account can join organizations in multiple available regions. Moving an existing organization is not a self-service setting.

Workspaces you create for yourself live in a personal organization. First-login setup creates the personal workspace in the current region without asking you to name it, then prepares a separate shared workspace for the coworker and colleagues you may invite. That shared workspace uses your first name, such as Taylor's team. The personal workspace carries your own name, so the switcher marks it Personal to tell it apart from a team; when it is not the organization you are in, it is listed first in the Switch organization list. Your personal organization has exactly one organization manager: you, its owner. People who collaborate in its workspaces join as plain members. Admin invitations and promotions are rejected, and a previously sent admin invitation is accepted as a plain membership. To those members, your personal organization shows up as Shared workspaces in their organization list and workspace switcher. They reach the workspaces you shared, but the owner-derived organization name, its link slug, and your owner identity stay hidden, and the organization's link address does not resolve for them.

A team organization is created, never converted. From a personal organization's Settings → Organization → Billing page, select Set up a team, choose the region first, give the new team a name, and review its seats before checkout. If your team uses seats on joining, it starts with one standard owner seat and adds colleagues after setup. Otherwise, choose the initial standard and premium seat mix. Review any offer and its renewal terms before continuing to payment. If you choose another region, setup continues in that region's app. Your personal organization and its workspaces are untouched, so they keep everything they had, and the people who collaborate in them stay guests there.

An existing team organization without an active Team subscription has a second entry on its own Billing page: Choose seats and start Team. That path chooses the same initial seat mix and checks out the existing organization instead of creating another one. It also works when the owner has no personal organization. Once the subscription activates, d5s opens the team's existing first workspace or creates one when the team has none. If workspace setup does not finish, the Billing page says so and offers Retry.

Leaving checkout without paying keeps one empty, unsubscribed team. Re-entering team setup resumes that same team instead of creating a second one. You can rename it. Teams cannot be deleted in-app.

The sidebar switcher opens on the organization you are in and lists its workspaces; a single Switch organization row below them opens the list of your other organizations in your current region. Each organization row names the workspace it opens, the one you last used there on this device or else its first, so switching organization is one selection. Each organization shows its logo, or the first letter of its name when it has none; your own personal organization shows your avatar. Other active regions appear underneath in a smaller Other regions section. Available destinations link to their regional app without claiming that your account has an organization there; an unavailable destination says Coming soon and has no link. A region switch asks you to choose an account on the destination's hosted sign-in screen; it does not transfer your current regional session. If a workspace link opens in a regional app where it cannot be found, d5s offers the other active regions while preserving the requested page path. Query parameters and fragments are not carried across regions. The workspaces of the organization you are already in are the first rows of the menu, so each of them is a single selection. On a narrow screen Switch organization expands in place when you tap it. Open Settings from your profile menu. The settings dialog groups Profile and Preferences under You and organization administration under Organization. Use the organization selector to choose an organization, then Workspaces to choose a workspace to configure. Changing the workspace you configure does not change the workspace you return to when closing Settings.

Organization Owners and Admins can change the organization display name with the Name field in Settings > Organization > General. Renaming changes the label shown throughout d5s without changing the organization slug or existing links. A personal organization still has only one organization manager, so only its owner can rename it. Owners and Admins of a team organization can also upload a logo there (PNG, JPEG, WebP, or SVG, up to 5 MB); it replaces the letter tile in the sidebar and the workspace switcher for everyone in the organization. A personal organization has no logo: it shows its owner's avatar.

The public d5s app opens sign-in for your default region. Signing in to another region does not transfer your current session or credentials.

An organization Owner or Admin also needs workspace administration access to manage an agent's Teams setup. Organization-level provisioning consent and each agent's channel activation are separate steps. See Teams agent setup.

Membership and policy

Workspace roles describe the maximum set of actions a person can take:

Workspace roles

Role	Main access
Owner	Full workspace control, including members, settings, capabilities, and deletion.
Admin	Manage workspace members, settings, skills, and connectors.
Member	Create and use workspace resources.
Viewer	Read-only workspace access.

Organization membership and workspace access are separate. A new workspace starts with its creator as the sole Owner; organization Owners or Admins then grant Admin, Member, or Viewer access to individual organization users or groups. Group assignments follow current group membership. Active organization Owners and Admins are automatically Admins of every workspace in the organization, including workspaces created later. This access follows their organization role and cannot be changed in the workspace. Plain organization members get workspace access only from an explicit assignment or an invitation.

Workspace Owners and Admins, plus organization Owners and Admins, can invite someone directly to a non-personal workspace. Accepting grants the selected Member or Admin role in that exact workspace. A new collaborator joins the organization as a plain member, while an existing organization role is preserved. Invitations are independent per workspace, so the same address can have pending invitations to multiple workspaces in one organization. The personal workspace cannot be shared by invitation; Invite people there creates a new workspace in your personal organization and opens its invitation form, so you invite people to that workspace instead.

Organization Owners and Admins create workspaces from two places. The workspace switcher at the top of the sidebar lists the current organization's workspaces; select the Create workspace plus button in its header, and the new workspace is created in the organization you are in. An organization that has no workspace yet shows Create workspace in the Switch organization list instead. The same action, with the full portfolio table beside it, lives at Settings → Organization → Workspaces. The switcher shows these create controls only for organizations where you hold the Owner or Admin role. Access is governed from each workspace's own Members tab; select a row in the Workspaces table to open that workspace. Use the organization selector before opening Workspaces when needed. Open a workspace to see its available General, Members, Browser, Network, and Developers tabs. Developers contains API keys; connected credentials remain in Connectors. Models and Providers are organization pages. On a narrow screen, use the Settings index, then the workspace and section selectors. Search settings can find Workspaces by related terms such as API keys; choose the workspace and tab after opening it. A plain organization member sees only accessible workspaces and no create or access-management actions. If that member has only one workspace, the Workspaces shortcut opens its General page directly.

Workspace Owners and Admins can change the workspace display name from Workspaces → workspace name → General → Workspace details. The slug is a separate, permanent identifier used in workspace URLs, so renaming leaves the slug and existing links unchanged. Portfolio-level organization administration does not provide a second rename control or bypass the need for workspace access.

Workspace Owners and Admins can set workspace instructions in Workspaces → workspace name → General → Instructions. Every agent in the workspace follows them in every chat, project, and agent conversation. Agent and project instructions add to them. Use them for rules that apply to all work, such as language, tone, and house style. Instructions guide agents but do not enforce approvals; use connector approval settings for that. There is no length limit. Every message includes the full text, so long instructions use more credits. If the instructions and the conversation are too long for the model, the message stops with a notice that asks you to shorten the instructions or start a new conversation. To remove the instructions, clear the text and save. Members can read the instructions but cannot change them. A change applies from the next message in each conversation. Work that is already running finishes with the previous text. Each change is recorded in the audit log.

To delete a non-personal workspace, a workspace Owner opens Workspaces → workspace name → General → Danger zone and reviews the content and connections that d5s will remove. The Owner acknowledges permanent deletion, enters the exact case-sensitive workspace name and an email code, then schedules deletion. Content can remain in the workspace. The workspace remains available for 48 hours, and new content is included in deletion. The Owner or any workspace Admin can cancel during that period. At the deadline, d5s stops new work and removes the workspace, its data, and its dedicated external agent connections. The completion email arrives when cleanup finishes. If the dialog shows Deletion needs attention, contact support. Personal workspaces cannot be deleted. Organization Satellite installations are independent of a workspace. Deleting a workspace removes its Satellite grants without deleting the organization's cluster installation.

Billing, usage, and audit are organization settings. They require an organization Owner or Admin. The Billing page shows paid seat quantities; see Plans and credits. For teams that purchase seats upfront, an invitation to the organization or one of its workspaces claims capacity and is refused when active members plus pending invitations fill the seat quantity. If your team uses seats on joining, an organization Owner or Admin reviews and authorizes any additional seat before sending. Pending authorized invitations carry no charge; acceptance adds needed capacity after successful payment or the displayed waiver. An existing active team member needs no extra seat. A personal organization's shared-workspace guests never become billable seats.

The organization Usage view shows spend, model and skill activity, and member, agent, and workspace totals. An administrator can inspect a run only when they also have access to its conversation. Filters help answer who initiated work, which agent handled it, and which workspace it belongs to. Historical entries remain in totals even when a current name is unavailable. Team totals remain the complete organization view.

Credits and spend controls

Workspaces in the same organization share credits. Paid plans use short and weekly pace windows for included and referral credits. Purchased credits remain usable after a window is full, and their spending does not fill those windows. Free organizations from before 4 October 2026 use their daily grant without additional pace windows. Your plan determines its allowance and renewal schedule.

An organization Owner can assign or clear a non-negative spend limit for any member. An organization Admin can do the same for ordinary members, but cannot change their own limit or another manager's limit. The limit measures that member's charged usage during the organization's current credit period and blocks new work they initiate after the limit is reached. It does not change their workspace or project permissions. Organization Owners and Admins can also set an organization spend limit and per-workspace spend limits on the Billing page; see Plans and credits.

Projects can then inherit access from the workspace or be restricted to explicit user and group grants. Workspace administration and project sharing are therefore related, but not interchangeable.

Shared catalogs

The connector guide shows how workspace credentials are added and how their tool permissions are reviewed.

Skills, connector credentials, and API keys are managed separately in each workspace. Models are managed once for the whole organization. Adding a workspace does not copy another workspace's credentials, secrets, projects, or conversations.

A Free organization starts with the Light level as its default and runs Light only. The current family list stays visible on the Models page but cannot be enabled while the organization is on Free. Paid organizations can use the levels and hand-picked models currently available to their account. Review Organization settings → Models for the current default and available choices. A downgrade to Free makes only Light available without deleting the saved paid-plan policy. After upgrading, saved paid-plan choices become available again when the account can still use them. Every workspace in the organization shares this one policy.

• The organization model policy determines which models people may select under the organization's plan and privacy requirements, and it applies to every workspace in the organization. An organization Owner or Admin sets it under Organization settings → Models. A new model family starts disabled until an owner or admin enables it. New versions of an enabled family become available automatically when the account can use them; see Administer d5s. Models marked as training on prompts require explicit confirmation, cannot be the default, and are unavailable when the organization requires models that do not train on prompts. An organization Owner or Admin manages that requirement from Privacy; a personal no-training selection protects that user's work without changing the shared catalog. The Models page lists models by publisher, marks the most expensive models with $$$, and names where each model runs, with an EU flag for models served through Amazon Bedrock or Azure OpenAI in the EU.
• Built-in platform skills are available to every project. Installed workspace skills become candidates that a project can pin and activate.
• Connector credentials are stored per workspace and attach to projects by default; each project can remove credentials it should not use.
• A Gmail or Microsoft credential bound as an agent mailbox is reserved for that agent's email channel; it is not automatically exposed to the agent as a general project connector.
• When a provider offers multiple connection methods, administrators choose the appropriate authorization and action boundary.
• Workspace API keys authenticate server and CLI integrations within that workspace.

Skills still require project activation. Agents get every workspace skill by default. Connectors follow the workspace default instead: adding one expands connector availability to existing and future projects, chats, automations, dashboards, and agents unless a project removes it.

Google connections and workspace privacy

Google content can be used for the work you authorize in this workspace. Tasks using AI may send relevant content to the AI providers used by the workspace. Disconnecting does not erase information already retrieved. See Google data protection for AI processing and stored-data guidance.

Check computer storage

If your workspace settings show Storage, workspace owners and admins can open Settings → Workspaces → workspace name → Storage. The tab shows capacity, used space and available space. Select Refresh to read current usage. It does not start a stopped computer.

Usage includes saved workspace files, browser profiles and filesystem overhead. System files are excluded. A stopped or unreachable computer shows an unavailable state instead of zero usage. If storage is full, free up space before saving new files. This page does not resize storage.