ActVox user guide

ActVox basics

A workspace is the unit where ActVox keeps your company context and work. Use one workspace for one brand, client, or operating team so the agent can reason from the right business context.

Your workspace can contain:

First workspace setup

1. Sign in. A new workspace opens on three doors: Connect my AI, Analyze my website, or Start blank.
2. Connect my AI copies a prompt into Claude, Codex, ChatGPT, or another client. Read and write are the powers it asks for. What it writes shows up here as pages you can open.
3. Analyze my website runs an analysis. Start blank opens the workspace so you can write the first page yourself.
4. Home then shows Get started, which says what to do next. When it reads You're set up, that heading opens Start here.
5. Add source material in Knowledge base. Files in Files & Media are not searched until you add them there.
6. Open ACTVOX.md for standing instructions the agent should consider on every turn: approval boundaries, terminology, voice, target geography, or source-quality rules.

A teammate invited into an existing workspace still confirms the company profile before the workspace opens. Company website, description, audience, and products stay editable in Settings.

Start here

Start here is a normal page under Home. It says how the workspace fits together, in five blocks: Connect your AI, Organize your workspace, Your sidebar, Knowledge Base and Memory, and Studio. Each block is about five lines and one Try it, which opens the real place. Notes you type between the blocks stay on the page. The title follows your language until you rename it. The page is not shared.

Open it from the account menu (Open the Start here guide) or from the command palette. If it was in Trash, that opens the same page again.

The first time you open Memory, Files & Media, Reports, Content, Calendar, or Brand DNA, a one-line strip explains the area, offers its main action, and links How it works to the matching Start here section. Knowledge Base, Artifacts, and pages get a short tour instead, pointing at the real controls. Each shows once. ActVox starts at most one of these, or any other tip, on its own every six hours, and none in your first day or while Get started is on Home. Take the tour in the account menu walks the screen you are on whenever you ask for it.

Good operating pattern: establish the business profile and source material before asking for a consequential strategy, report, or content plan. Better context produces more useful and more attributable output.

Sidebar navigation

The left sidebar is the map.

Content, Calendar, and Brand DNA are the Studio tools: drafts, when each draft goes out, and the colours, type, logo, and voice every image and draft follows.

Skills and Connectors are not a sidebar root. Skills open from the chat composer’s ✨ menu. Connectors open from Connect your AI and from the Skills and Connectors tab.

---

The Workspace OS is the main work surface. It keeps live documents, structured work, context, and agent output connected to the same workspace.

Get started on Home says what to do next. Start here, a page under Home, says how the pieces fit. Open it from the account menu or the command palette.

Workspace settings

Open Settings from the workspace controls to maintain the workspace identity and marketing profile.

Click Save after changing settings. Treat the destructive Delete workspace control carefully: it requires typing the workspace name to confirm.

Settings and preferences

The workspace provides several settings areas. Availability may vary by your account and deployment.

Agent preferences

In Settings → Agent, you can set the agent name, default response language, greeting, and communication style. Available built-in personas include Professional, Friendly, Concise, Detailed, and Custom.

For standing instructions, use ACTVOX.md in the Context section of the workspace tree. It is the current editable instruction surface that the agent reads on every turn. The older system-instructions settings field is retained for legacy setup but is not the place to maintain live instructions.

Workspace navigation

Use tabs to work across multiple pages, databases, conversations, and outputs without losing your place. The active tab appears in the center workspace area. Open related work in separate tabs when comparing a brief to a database, report, or agent result.

Useful navigation habits:

• Keep business-wide guidance in ACTVOX.md, Profile, and Strategy, not scattered across campaign pages.
• Keep the working system - planning, execution, and tracking - under Workspace.
• Put raw evidence in Knowledge base or Files & Media, then cite or link it from pages.
• Use Content and Artifacts as output review queues rather than as the only source of truth.

---

Pages are durable documents for briefs, research notes, plans, reports, playbooks, and decisions.

Create a page

You can create pages from the Workspace tree or from inside another page.

1. In Workspace, use the add control for the target location.
2. Choose Page and give it a clear, action-oriented title.
3. To create a nested page, open the parent page and insert a Page block, or create it in the corresponding subtree.
4. Start writing. Changes save automatically after a short pause.

A useful naming convention is: YYYY-MM - outcome - audience or channel, for example 2026-08 - LinkedIn founder narrative - B2B SaaS.

Use blocks and slash commands

Type / in the page editor to open the block menu. Search by name, then select a block. You can also use the block handle to insert, move, or change a block.

Format and organize pages

• Use headings for a scannable hierarchy; table of contents blocks use that hierarchy.
• Use a callout for the decision, assumption, risk, or owner that a reader must not miss.
• Use to-do blocks only for lightweight page-local work. Use a database when work needs owners, dates, reporting, or repeatability.
• Add a page icon or cover to distinguish high-traffic documents.
• Link related pages rather than copying their content. This keeps evidence and decisions current.
• Use the comments panel for collaboration and the version/history controls for review when available.
• On a phone, you can comment while staying in Reader. Select text and choose Add comment to discuss that passage. Editing permission is required.
• When an agent suggests changes on a phone, choose Review to enter Edit and jump to the first change. Accept all applies the pending changes; Reject all dismisses the suggestion. Editing permission is required.
• To change block order on a phone, enter Edit and choose Reorder. Use the up/down buttons to move a block; each move has its own undo step. Close the sheet or use Back to return to the page. Reordering is unavailable while an agent suggestion is pending.

Add attachments and media

Insert an Image, Video, Audio, or File block, then choose the file to upload. You can also add page attachments. Use descriptive titles and surrounding explanatory text so another teammate - and the agent - understands why the material matters.

3D models

Insert a 3D model block and choose a GLB or glTF file (up to 50 MB). The block shows the model in an orbit-and-zoom viewer with the file name, size and format in the corner. Everything about the block can be changed in place:

• Settings (the gear in the frame) opens a details table inside the same frame: alt text, a caption shown under the model, auto-rotate, camera controls and height. Save writes all of it at once; Cancel discards it. The viewer previews the draft while you edit.
• More offers Replace model, Set AR file (a USDZ companion so iPhone and iPad can open the model in AR), Poster from current view or Upload poster… (the still used for PDF export and print), Remove poster, Download and Copy link to block.
• Open in new tab shows the model on its own page; Fullscreen enlarges it in place.

A USDZ is an AR companion, not a model: add the GLB or glTF first, then set the AR file. Replacing the model clears the poster and the AR file, because both pictured the old file. Shared pages and exports keep the caption and camera settings.

---

Databases make recurring work structured, filterable, and reviewable. Typical examples include content calendars, campaign trackers, research libraries, CRM-style lists, competitor trackers, and task boards.

Create a database

1. In Workspace, choose the add control and select Database.
2. Choose whether to create a full-page database or insert one inside a page.
3. Name the database for the operating job, not the tool - for example, Q3 Content Pipeline rather than Content table.
4. Create the first properties and views before importing a large amount of data.

Build a useful schema

Every database has rows, which open as full pages, plus properties that describe each row.

Start small. For a content pipeline, use:

Available property types can include text, number, select and status, date, person, relation, URL, phone, email, formula, and system fields such as created time, last edited time, created by, last edited by, and ID.

Choose the right view

Use filters to hide irrelevant rows, sorting to create a decision-ready order, and group-by to make workflow states visible. A database’s shared link respects its saved view configuration, including filtering and order.

Work in a table

• Hover a row to see its controls on the left: + adds a row below it (hold Alt to add it above), the grip moves the row when you drag it and opens the row menu when you click it, and the checkbox selects the row.
• Choose Open in a row's name to read and edit the row as a page. In a full-page database the row opens beside the table, and the table stays editable; View settings → Open pages in switches between Side peek, Center peek and Full page.
• Click a column's header for everything about that column: filter, sort, calculate, freeze the columns up to it, wrap its text, hide it, change its type or edit its options.
• The line under the table shows one calculation per column, such as a sum or a count, and keeps it with your view.
• Choose Search in the view bar to show only the rows that contain every word you type.
• Select several rows to change them together: the bar above the table sets a property on all of them, duplicates them or deletes them. Shift-click selects a range; Escape clears the selection.

Linked and inline databases

• Use an inline database to keep a small working table inside a planning page.
• Use a full-page database for a team operating system that needs many views.
• Use a linked database view to show the same source database in a different page and context. For example, show only LinkedIn drafts on a channel plan page without duplicating the underlying items.

---

Share a page or database

Pages and databases can have share links. Open the Share control in the object header, choose an audience, then create and copy the link.

Changing the audience of an active link rotates its token. The old link stops working, so notify anyone who relied on it.

You can also duplicate a public page into your active workspace. Sign in, choose Duplicate to my workspace, and edit the independent copy; the source workspace and page stay unchanged.

Stop sharing and audit live links

• Open the object’s Share control and choose Stop sharing to revoke one link.
• Open Settings → Shared links to review every active link in the workspace, including the object, audience, creator, and creation date.
• Use Revoke all only when you intend to invalidate every active page and database share link in the workspace.

Collaborate well

• Keep decisions in a page or database record, not only in a chat message.
• Use comments and review states for feedback on pages and database rows where available.
• Share the smallest useful object. A focused brief is safer and easier to act on than an entire workspace export.
• Before creating a public link, check for client data, credentials, personal information, internal planning, and unpublished work.

Ask ActVox in a comment

Where a workspace owner or admin has turned on Settings → Agent → Answer @actvox in comments (off by default), members can write @actvox in a page comment and ActVox answers in the same thread.

• Select text and add a comment to ask about that passage. ActVox sees the thread, the quoted passage, the page title, and an excerpt of the page.
• The reply reads "ActVox is thinking…" and is replaced by the answer. You get the usual reply notification. If the answer cannot be produced, the thread gets a short notice instead of silence.
• Editing the comment you wrote never produces a second answer.
• ActVox can do no more than you can. When you ask for a change and can edit the page, ActVox proposes the edit and links the review; nothing changes until a person accepts it. A viewer's question only gets an answer.
• Each answer uses the workspace's credits, and a workspace gets at most 20 answers an hour. After that, the thread says the limit is reached and to try again later.

---

The ActVox agent works from workspace context, attached material, relevant pages, and supported integrations. It is designed to create durable results - pages, plans, drafts, records, and artifacts - rather than only returning disposable chat prose.

Ask good questions

Use a clear outcome, relevant context, and a boundary. For example:

Review the competitor notes in this workspace, create a one-page positioning recommendation, and do not change our existing strategy page.

You can reference pages, files, and workspace objects in a conversation. Keep source material current so the agent can ground its output.

Attach files to a conversation

Use the attachment control in the composer to add authorized source material to the current request. ActVox uploads the file to durable workspace storage before it sends the message. While an upload is in progress, Send and the Enter shortcut remain disabled. Wait until the attachment appears in the composer; if the upload fails, resolve the visible error and attach the file again.

The agent can extract bounded text from PDF, DOCX, TXT, Markdown, CSV, JSON, XML, HTML, and other text-based files. Images, audio, and supported video use their media-processing paths. A successfully attached file keeps a persistent serving URL in the conversation, so the message and attachment remain available after reload. Extraction still depends on a readable file: scanned PDFs without text, encrypted documents, corrupt files, and unsupported binary formats may require another format or explicit context in the prompt.

Tell the agent what the file is and what to do with it. For example:

Read the attached customer interview notes, identify recurring objections, and create a cited summary page. Do not infer facts that are not present in the document.

Do not attach credentials, secrets, or material you are not authorized to process.

Plan

Use Plan for work that is multi-step, ambiguous, cross-functional, or consequential.

A plan should make the proposed work inspectable before execution. It can include scope, evidence to use, assumptions, steps, expected outputs, risks, and approval points. Plan is appropriate for requests such as:

• Create a 90-day content strategy from research and the current brand profile.
• Audit competitor positioning and recommend a category narrative.
• Design a research and reporting workflow before changing a database.

Review the plan, correct assumptions, and approve the next step in the conversation. Do not treat a plan as proof that an action has been completed.

Act

Use Act when you want the agent to execute a supported operation. Act can create or update supported workspace objects, organize material, produce reports, generate drafts, and run eligible analysis flows.

ActVox verifies required effects before it claims success. For example, when asked to create a page or content draft, the expected result is a real workspace object you can open and edit - not only a pasted response in the conversation.

Low-risk, reversible workspace writes may run directly when your request is explicit. Destructive, bulk, publishing, live-document, or otherwise high-impact actions can require review or approval. External availability also depends on integration permissions and product policy.

Skills

Skills are reusable, versioned instruction packages available in a workspace. Access them from the chat composer’s ✨ menu or through their associated slash commands when available.

Use a skill when the task benefits from a repeatable procedure, such as onboarding context capture, creating a company profile, or producing an initial content draft.

Good practice:

1. Read the skill description and expected output.
2. Confirm it matches the workspace and intended outcome.
3. Run it with the specific information it needs.
4. Review the generated page, draft, or artifact before sharing or publishing.

Skills do not bypass workspace permissions, action allowlists, or approval requirements. User-authored skills are versioned and should not be silently rewritten by autonomous improvement workflows.

---

ActVox can connect supported sources, platforms, and agent tooling to a workspace. Connections are scoped to the workspace and subject to the connected provider’s permissions, availability, quotas, and policy.

Connect your AI

Open Connectors in the sidebar and choose Connect your AI.

1. Pick the AI you use. Some run in your browser (Claude, ChatGPT); others run in your terminal (Claude Code, Codex).
2. For a terminal client, copy the prompt it shows and paste it into the client. It sets up the connection itself and opens an ActVox window. For a browser client, add ActVox to it as the steps show.
3. In the ActVox window, choose this workspace and click Allow access. Read and write are chosen for you; Choose permissions changes them.
4. The flow says the AI is connected. Copy the first task it offers and paste it into the AI. It asks you a few questions, then saves its plan here as a page, and Open it takes you there.

Each connected AI has its own Settings: rename it, turn on Mentions and tasks so it can be @mentioned and assigned work, and choose who can use it.

Availability vocabulary

The UI uses these exact availability states: supported, canary_passed, verified, verified_read, documented, unavailable and blocked. verified and verified_read are permanent approvals based on real production connections: verified means a write was confirmed in production, verified_read means reads only. A label says how far ActVox has verified a client end to end. It is not the access level: a connection's permissions are what you approve at consent. The state is documented separately for each product: MCP grants authenticated tools and workspace data; a skill supplies instructions for a local agent.

AI-agent availability

Setup steps for each agent are on the Agents page.

Keep the three stores separate

Profile, workspace instructions, and the Knowledge Base are three separate stores. A connection does not merge them into one memory blob.

1. Profile stores the business portrait and identity fields.
2. Instructions store how the agent should work with you.
3. The Knowledge Base stores sources such as sites and documents; indexing can spend credits.

ChatGPT — MCP — verified

• Add ActVox as a custom connection in ChatGPT Developer mode, then authorize the hosted MCP endpoint https://api.actvox.com/mcp with OAuth.
• Start with read access for one workspace. ChatGPT has no ActVox skill installer; use the Codex tile for a local skill.

Claude (hosted) — MCP — verified

• In Claude, open Customize → Connectors → Add custom connector, paste https://api.actvox.com/mcp, and choose Sign in now with Claude’s published OAuth identity.
• Team and Enterprise owners can add the connector once in organization settings, but each member still signs in and consents individually. Claude Code is a separate tile.
• Approved permanently on 2026-10-03 from production use: live connections wrote and the result was confirmed by read-back, so its setup panel reads Integration: Tested.

Claude Code — MCP verified_read; skill supported

• The hosted MCP path is approved permanently at verified read: live Claude Code connections read workspace data in production, and no write through its own connection has been confirmed yet. Run claude mcp add --transport http actvox https://api.actvox.com/mcp, then claude mcp login actvox and complete consent.
• The installable skill is supported for the claude target. Use the Claude Code tile for the installer, key setup, and local verification.

Codex — skill supported; MCP verified

• The installable skill is supported for the codex target. Use the Codex tile to install it, issue a workspace key, and run the read-only doctor and capabilities checks.
• Hosted MCP is approved permanently: Codex’s production use runs through ChatGPT’s connector and includes writes confirmed by read-back. To connect the Codex CLI with its own identity, run codex mcp add actvox --url https://api.actvox.com/mcp, then codex mcp login actvox and complete consent. A local skill install is not hosted MCP support.

Hermes — skill supported; verified through the ActVox CLI

• The installable skill is supported for the hermes target. Use its tile for the skill installer and workspace-key setup.
• Hermes works with ActVox through the skill and the ActVox CLI (a workspace key or a CLI login). That path is approved permanently on production writes, and its setup panel reads Integration: Tested over the ActVox CLI; the tile itself reads Connected once you connect one here.
• Hermes’ own hosted MCP connection stays available: run hermes mcp add actvox --url https://api.actvox.com/mcp --auth oauth, then hermes mcp login actvox and complete consent. The skill’s instructions do not grant workspace data by themselves; keep the key in the agent’s protected environment.

Grok — MCP — verified

• In grok.com, open Connectors → New Connector → Custom and add https://api.actvox.com/mcp with the OAuth values shown on the Grok tile.
• Grok has no ActVox CLI or skill installer. The hosted connection is approved permanently: live Grok connections wrote in production and the result was confirmed by read-back.

OpenClaw — verified through the ActVox CLI; no installer

• OpenClaw works with ActVox through the ActVox CLI (the ActVox CLI tile: a CLI login or a workspace key). That path is approved permanently on production writes, and its setup panel reads Integration: Tested over the ActVox CLI; the tile itself reads Connected once you connect one here.
• Its own hosted MCP connection stays available: run openclaw mcp add actvox --url https://api.actvox.com/mcp --transport streamable-http --auth oauth, then openclaw mcp login actvox and complete consent. There is no catalog skill or installer target for it.
• The manifest still lists local_skill as a limitation, but OpenClaw has no catalog skill: true flag and is not an installable skill client. Do not claim it is supported or add an installer.

Short first test

After a supported skill or an available MCP connection is ready, send this read-only Knowledge Base smoke test:

Run a read-only Knowledge Base smoke test. Tell me which workspace you can access and list the titles of the first three Knowledge Base sources. Do not write or save any personal information unless I explicitly confirm the exact fields and values first.

This is a smoke test, not the five-step onboarding. If onboarding follows, ask before each write and read back the profile, instructions, and Knowledge Base changes separately.

Manage and remove

• For MCP, the Connectors page shows the grant, last call, and verified effect; pause, resume, or revoke access there, then remove the connection in the provider.
• For a skill, revoke its workspace key on the Connectors page and remove the installed skill from the local agent.
• If a consent page says the client is not approved, the current tile policy is authoritative. Retrying does not change a documented, unavailable, or blocked state.

Your agents and your role

• Anyone with the editor role or above can connect their own agent, through a consent page or with a key on a connector tab. You name the agent when you connect it. It is private to you until an owner or admin shares it with the workspace, and only you see its connections.
• An agent never does more than the person who connected it can do now. An editor's agent cannot share, publish or change workspace settings; if you become a viewer, your agent can only read; if you leave the workspace, it stops working.
• On Free, AI connectors count for the whole organization: a product another member already connected adds no new connector.

Automation boundaries

An available connection does not mean every action is automatic or approved. Publishing, paid activity, destructive updates, and high-impact external actions can require explicit approval. ActVox does not guarantee external platform availability or campaign outcomes.

---

Workspace and organization administration

Workspace access follows the authenticated user and workspace or organization boundary. In an organization, administrators can manage organization membership, invitations, and roles through the organization controls.

Use the least authority necessary:

• Give members access only to the workspace and information they need.
• Restrict administrative roles to people who manage membership, settings, or high-impact actions.
• Review organization invitations and member roles regularly.
• Remove access promptly when a contractor, client engagement, or employment relationship ends.

API keys

Open Settings → API keys to create and manage API keys.

Prefer a project-scoped key over a multi-project key whenever possible. The secret value is shown only when created. Store it in a proper secret manager or the approved tool environment, not in a page, chat, uploaded file, screenshot, or source code repository.

Revoke a key immediately if it may have been exposed, is no longer needed, or belongs to a departing collaborator. You can also delete a revoked key to remove it from the list.

Account and sharing security

• Open Manage account from the account menu: Account (name, email addresses, connected accounts), Security (password, passkeys, active devices, delete account), Credits (your ActVox Credits), and Billing (payment methods and statements). Organization admins open Manage organization from the gear on an organization row: General (name, logo, leave, delete), Members (invitations and roles), Credits (shared wallet and seats), and Billing.
• Use the account security controls for your personal account security settings.
• Use Settings → Shared links to audit what is externally accessible right now.
• Treat public links as public. Do not rely on obscurity of the URL as a security control.
• Rotate a link by changing its audience or revoke it and create a new link.
• Use organization-only links when the material is intended only for your organization.

---

Reports are durable research and audit outputs connected to the workspace. They can capture analysis of websites, markets, competitors, SEO/AEO, social presence, local presence, and other supported business signals.

Create or run a report

1. Open Reports in the Context section of the Workspace OS.
2. Use Run new analysis when it is available.
3. State the question, scope, sources, market, or target audience clearly.
4. Review the report’s evidence, assumptions, and recommendations.
5. Turn accepted recommendations into a Strategy, a page, a database item, or a task.

The standalone reports route redirects to the Workspace OS; the Workspace OS report entry is the canonical place to find and continue report work.

Review a report critically

A report is evidence-informed output, not a guarantee. Before acting on it:

• Check the source quality and date.
• Separate observed facts from hypotheses and recommendations.
• Confirm anything that affects legal claims, pricing, budgets, external commitments, or publishing.
• Link the report to the strategy or decision it informed.

---

Strategy is the durable workspace artifact for the choices that guide execution. It should connect research to priorities, audiences, positioning, channels, campaigns, and measurement.

Use Strategy for questions such as:

• Which audience segment should we prioritize this quarter?
• What category narrative and value proposition should guide content?
• Which channels deserve investment, and what will we measure?
• What must be true before we launch a campaign?

Recommended strategy structure

1. Objective - the commercial or strategic outcome.
2. Audience - who matters most, their context, and the job they are trying to do.
3. Evidence - reports, sources, research, and customer signals.
4. Positioning - category, differentiated value, proof, and objections.
5. Strategic choices - what to prioritize, avoid, sequence, or test.
6. Execution system - content, campaign, research, and operating work linked to pages or databases.
7. Measures - leading signals, outcome metrics, owner, review cadence, and decision rules.

Do not make Strategy a storage place for every idea. Keep it decision-oriented and link to deeper evidence elsewhere.

---

Design.md is a Context entry for durable design direction. Use it to make creative work more consistent across people, pages, and agent-assisted output.

This guide interprets “Design my” as the Workspace OS Design.md context surface.

A strong Design.md can include:

• Brand personality and visual principles.
• Color and typography guidance.
• Image, video, illustration, and layout direction.
• Examples of what to emulate and what to avoid.
• Accessibility and localization requirements.
• Channel-specific constraints, such as LinkedIn carousel dimensions or webinar visual standards.

Use concise, testable language. For example, write “editorial, precise, high-contrast, documentary imagery; no generic AI blue gradients” instead of “make it modern.” Link approved source assets from Files & Media or Knowledge base.

---

The Knowledge base is the workspace source library. Use it for materials your agents should be able to search, cite, and revisit. Uploads elsewhere are not searched until you add them here.

Add sources

You can add:

• A web page, with Add a link. ActVox reads the page and indexes it. Indexing uses ActVox Credits.
• A file that is already in Files & Media, with Add to Knowledge Base.
• A PDF or a Word document (.doc or .docx) from this page.
• Discovered sources from an eligible industry, business type, and location search.

Open Knowledge Base in the sidebar. A ready source reads Ready and shows how many sections were indexed. Search the knowledge base to confirm the source is useful.

Find and use evidence

Use Knowledge base search to retrieve relevant workspace sources before writing a brief, report, strategy, or content asset. Source discovery can help identify candidates, but review discovered sources before treating them as authoritative. You can rate discovered sources to improve future discovery relevance.

Maintain quality

• Prefer primary sources, approved brand material, customer research, and dated market evidence.
• Remove stale, irrelevant, duplicate, or untrusted sources.
• Keep confidential material in the appropriate workspace and never add secrets.
• Use meaningful source titles so teammates can assess a result without opening every file.
• Re-index an updated source when the source content has materially changed.

---

Files & Media holds everything uploaded to the workspace: documents, images, and video.

Use Files & Media when you need to:

• Preserve the original file before turning it into a page or report.
• Give the agent an authorized attachment to reference.
• Preview, organize, rename, move, or remove workspace files.
• Retry an upload that failed.

Upload carefully

1. Open Files & Media in the sidebar and use Upload, or use an upload control on the surface you are in.
2. Select the file and wait for its upload state to complete.
3. Rename or place it where the team will find it.
4. Add it to the Knowledge base when agents should search it. An upload is not searched on its own.

Uploads are not automatically public. Sharing a page or database is a separate action.

---

Memory holds short facts about this workspace. You add them with Remember. The chat and a connected agent can add them too. Facts the chat stored appear under Remembered in chat. A fact that is only yours is marked so. Forget removes one you are allowed to remove.

Examples of useful memory:

• A priority audience, a positioning constraint, or a target region.
• An approved terminology rule or a known objection.
• A recurring operating preference that should shape future work.

Memory is workspace-scoped. Treat it as short context, not as a secret vault and not as a substitute for a page or a source.

Use memory responsibly

• Put standing operating instructions in ACTVOX.md.
• Put files and web pages agents should search in the Knowledge base. Keep the original file in Files & Media.
• Keep a decision in Strategy, a report, or a page where it can be reviewed and revised.
• Do not rely on memory alone for a critical claim. Confirm it against a current source.

---

Conversations are the agent work surface. They live in the Agents area of the Workspace OS and keep the discussion connected to the workspace’s context and objects.

Use conversations for work, not just questions

A productive conversation usually has:

1. Outcome - what you need delivered.
2. Context - relevant pages, sources, files, or business constraints.
3. Boundary - what the agent may and may not change, publish, or assume.
4. Review point - when you want a plan, draft, recommendation, or approval request.

Example:

Plan a competitor positioning review for our UK market. Use the knowledge-base sources and the current strategy. Create a page with evidence and recommendations, but do not alter Strategy until I approve it.

Manage conversation output

When a conversation produces something worth keeping, ask the agent to save it as a page, report, strategy update, content draft, database item, or artifact. Open the resulting object and review it outside the chat. This creates a durable record and makes the work reusable by the team.

Use attached files, referenced pages, and skills deliberately. They improve grounding but do not remove the need for human review.

---

Studio is where marketing work is made. It is four tools: Content, Calendar, and Brand DNA in the sidebar, and the Media studio inside a draft. A draft is a post for one channel, with its images or video.

Content

Content is the output area for marketing assets such as drafts, adaptations, and media-oriented work. It is designed to connect content back to workspace strategy, research, and source context.

Use Content to:

• Create and review draft marketing assets.
• Organize variants and adaptations.
• Link content to the relevant audience, campaign, channel, strategic theme, and evidence.
• Prepare work for a content calendar or publishing workflow.

Content workflow

1. Start with a strategic intent and a specific audience.
2. Give the agent approved sources, positioning, and channel constraints.
3. Ask for an editable draft - not automatic publication.
4. Review factual claims, voice, differentiation, CTA, and compliance.
5. Save the approved draft in Content and connect it to a campaign or database record.
6. Use the relevant integration or publishing process only after the required approval.

Draft, adapt, and schedule a post

The fastest path from an idea to a scheduled post runs through the agent and a calendar database.

1. Ask the agent for a draft and name the platform, the audience, and the goal.
2. Ask for adaptations of the approved angle for the other platforms you use.
3. Review each draft in Content and edit the claims, voice, and call to action.
4. Set the status to Scheduled and pick the publish date on the linked calendar record.
5. Publish through the connected account only after the required approval.

Example request: "Draft a launch post for Instagram for local cafe owners, then adapt it for LinkedIn and X, and put both on next week's calendar."

ActVox can generate and adapt content, but it does not guarantee reach, rankings, engagement, conversions, or revenue.

Calendar

Open Calendar to see when each draft goes out. New content there starts a draft. Approved posts publish to Instagram or LinkedIn once that account is connected.

Brand DNA

Brand DNA is the colours, type, logo, and voice that every image and draft follows. Open it in the sidebar. Scan my brand reads a website or a supported social profile and fills those fields. Reference sites are a separate list: they steer composition and do not change the palette or the logo.

Media studio

Open a draft to edit its images, a carousel, or video. Image, Carousel, and Video are modes of that one editor. Generated images and video also appear in Files & Media.

---

Artifacts are generated workspace outputs that are not simply a page or content draft. They can include results from supported agent or media-generation workflows and retain the context needed to inspect or reuse the work.

Use Artifacts to:

• Review a generated deliverable before deciding where it belongs.
• Keep output provenance connected to the workspace.
• Promote a usable output into Content, a page, a report, or another operating record.
• Separate experimental or generated material from final approved source-of-truth documents.

Review before reuse

Before sharing, publishing, or relying on an artifact:

• Open it and inspect the actual result.
• Check that it matches the requested audience, brand, source, and channel constraints.
• Verify factual assertions against the original evidence.
• Confirm rights, permissions, and platform requirements for any external use.
• Move or link the approved result into the page, database, Content item, or campaign where the team will operate from it.

---

Operating principles

1. Context first. Keep the business profile, instructions, evidence, and strategy current.
2. Pages for thinking, databases for repeatable operations. Do not turn every page into a table or every table into a document.
3. Plan before consequential work. Review scope and assumptions before execution.
4. Act with review. Inspect created objects and approve high-impact external activity explicitly.
5. Preserve evidence. Link recommendations to reports, sources, and decisions.
6. Share narrowly. Prefer the smallest audience and the smallest object that solves the collaboration need.
7. Protect secrets. Do not place credentials, tokens, or sensitive personal data in public links, pages, prompts, or uploaded files.