Dashboard and Inbox
Dashboard shows an overview of recent and active work. Open Inbox for work needing attention, then follow the item to its Run, approval, or source record. A summary is not the complete history.
Start with a personal Entity, then organize Spaces, folders, members, threads, context, files, Markdown artifacts, search, and bookmarks.
A Space holds the conversation and work for a project. An Entity owns Spaces, membership, and billing.
Choose an available sign-in method. For email signup, choose Create account, enter your details, follow the verification link, then sign in. Existing users can sign in directly.
First sign-in creates a personal Entity and a Space named Personal. Your Entity may be named My Swarm or include your name; Personal is also an Entity type label. Select the name actually shown in your switcher. No company setup is required.
Use the Entity switcher when working with more than one organization. Check the selected Entity before creating a Space or changing access or billing.
Use the sidebar for account-wide destinations and the current Space's navigation for its project records.
Dashboard shows an overview of recent and active work. Open Inbox for work needing attention, then follow the item to its Run, approval, or source record. A summary is not the complete history.
Use the conversation for discussion, Tasks for saved work briefs and dependencies, Runs for execution attempts, and Records for artifacts, prompts, and evaluations. Open an individual record for details; use page controls for older items.
Right-click a supported message, result card, or resource row for its available actions. Messages also offer Message actions; cards offer Open item actions. Use these overflow buttons on touch devices. Menus depend on your access and the item's current state.
Personal Profile and Settings are separate from Space settings and Entity administration.
Select your name or avatar in the sidebar. In Profile, edit Name, Language and region, or Time zone, then Save changes. Sessions lets you review and revoke offered sessions; Account includes Sign out and account lifecycle controls.
Open Settings from the sidebar. Choose Appearance: Light, Dark, or System; Text size: Default or Large; and Compact sidebar or Reduce motion as needed.
Select Save changes to apply these preferences. They are saved on this browser, not promised to sync to other devices. System reduced-motion preferences also apply.
Use one Space for work that needs a shared record and audience. Management controls depend on your access.
Open Spaces and choose Create Space. Select the owning Entity when offered, enter a name and optional description, then submit. Open the new Space to begin.
Open Space settings and use Details to change its name or description. Save the section before leaving; unsaved changes are not applied.
New Spaces start private. Review Access and Sharing before adding sensitive material. Creating a Space does not by itself connect an external runtime.
Folders arrange Spaces in your sidebar. They are not a new access boundary.
Open a Space's sidebar menu and choose Move to folder. Select an existing folder or enter a new folder name, then save.
Use New folder when available, or open a folder's menu to rename it. Expand and collapse folders to keep the sidebar manageable.
Delete folder removes the grouping. Its Spaces remain available and become unfiled; it does not delete their conversations or results.
Entity membership and Space access are separate. Use the smallest access profile that fits the work.
If a person is not available in the Space access picker, ask an Entity administrator to invite them from the Entity's Members section first.
Open Space settings and Access. Select a person or Team, choose one of the offered access profiles, and select Add. Check the collaborator list after saving.
Use Remove on an assignment you can manage. A person may still have access through a Team or another assignment. Review those paths separately rather than assuming one removal blocks all access.
Public discovery, signed-in viewing, and permission to collaborate are different settings.
In Space settings, open Sharing and review Visibility. Before making a Space public, check its content and prompt visibility settings. Do not publish secrets or material you cannot share.
Public collaboration lets signed-in non-members connect when enabled and permitted. It is not anonymous editing. The automatically managed personal home Space cannot enable public collaboration; this is not a restriction on every Space you create in its Entity.
Review the Space through Discover and check the configured detail level for signed-in public viewers. Changing visibility does not erase copies that viewers already received.
The conversation is the shared work record. A normal message is not automatically an agent request.
Open the Space conversation, leave the composer in Message Space mode, write your message, and send. Use Ask agent only when you want to start agent work.
Open the reply or discussion action on a message or result card. Write the follow-up in that discussion so it stays anchored to the original entry.
Load earlier conversation entries when needed. Open a result card to inspect its linked record; a short card is not necessarily the complete result.
Context links identify material for continued work. They are not copies and do not override access checks or model limits.
Open a message, file, artifact, or Run's available actions and choose Add to context where offered. Prefer current requirements, decisions, and evidence over unrelated history.
Review the Space's context before asking for work. Tell the agent which sources and outcome matter; adding context does not guarantee every byte fits into a model request.
Use Remove from context to stop including an item as active context. This removes the link, not the original message, file, artifact, or Run.
Files provide input; artifacts are saved records or outputs. The available preview depends on the content type.
Use Attach files in the composer for text, code, logs, Markdown, JSON, YAML, or CSV. Attach up to 8 non-empty files, at most 25 MiB each and 100 MiB total per message. This is not a general image, audio, or PDF attachment flow.
Sending uploads the attachments before posting the message. Wait for completion rather than sending again. Correct rejected files or retry a failed upload. For larger content, use the Space context upload flow when offered and follow its limits.
Open an artifact from its result card or Records. Use Preview for rendered content, Source when available for raw text, and Details for metadata and source links. A shortened preview is not the full file.
Messages and supported text artifacts render Markdown. Keep the source simple enough to read without formatting.
Use # headings, blank lines between paragraphs, - list items, and numbered steps. Use **bold** for emphasis and [label](https://example.com) for links.
Use backticks for short code and fenced code blocks for longer examples. Include source links and distinguish observations from recommendations.
Markdown supports tables and quotes, but is not a way to execute HTML or scripts. Do not assume arbitrary embedded media will render. Compare Preview and Source when formatting looks wrong.
Search and bookmarks help you return to records you can still access.
Open Search, enter a term, and choose All accessible Spaces or a particular Space. Narrow by record type, submit, and follow the result to its source. Use the page controls for more results.
Use the bookmark action on a message or resource when offered. Open Bookmarks, or the Space's bookmark panel, to return to saved work.
Choose Remove bookmark on a saved item. This does not delete the source. Bookmarks do not preserve permission to a record after your access changes.
Check the current audience and state before repeating an action.
Check your account, active Entity, filters, and later pages. Ask an administrator to confirm access. A saved link or bookmark cannot bypass a revoked permission.
Read the reason beside the control. You may need a different access profile, an available runtime, or an administrator's change. Reload after the underlying issue is fixed.
Check the conversation or record before sending again. Restore connectivity and refresh the current view; avoid creating a second request just because an acknowledgement was delayed.