# Codaroq Workspace

## Start a team

Install the official ZIP through WordPress **Plugins → Add New → Upload Plugin**, activate it and open **Workspace**. Create a workspace, then use **Team** to invite existing WordPress users. An invitation belongs to its named recipient. Creating WordPress accounts remains a WordPress administration task.

There are no paid seats, licence keys or artificial limits on workspaces, boards or documents. Storage, database capacity and server resources still apply. Large lists load in pages; use **Load more** to continue.

The interface uses the current WordPress user's language, with English and German built in. Dates retain their time zone. Browser-local date entry is converted to a precise instant; the calendar can display another IANA time zone such as `Europe/Zurich`.

## Choose access deliberately

Workspace roles are owner, manager, editor and viewer. Private objects belong to their owner. Shared objects use workspace membership; restricted objects have explicit grants. A child cannot grant access beyond its parent. Being a WordPress administrator does not bypass membership or private-object access.

Use the sharing dialog to review visibility and grants. Removing membership also removes access through old links and previously completed mutation receipts. A conflicting edit asks you to reload the latest version rather than silently replacing someone else's changes.

## Pages and knowledge

Create pages and arrange them under parent pages. Add headings, paragraphs, checklists, tables, internal links and private attachments. Templates provide reusable content. Tags, search, favourites and recently used items help you find it again.

Files are stored privately with Workspace data. Downloading a file checks current object and parent rights. File bytes are excluded from normal listings, history and structured content exports. Supported uploads are PNG, JPEG, GIF, WebP, PDF and UTF-8 text/Markdown/CSV/JSON/ICS, up to 5 MiB per file.

**History** shows earlier versions. Restoring creates a new version. Archive and trash are separate views with recovery actions. Deactivation retains the database; deleting the plugin does not constitute a verified data erasure or backup.

## Tasks and structured databases

Tasks support status, priority, responsible members, deadlines, reminders, repetition, dependencies and parent tasks. Use the board or a task's status selector to move work. An unfinished dependency prevents completion. Reminders and repeated occurrences run through WordPress cron; configure reliable site cron for low-traffic sites.

Databases define typed fields and saved views. Available views are table, board, calendar, list, gallery and timeline. Select a compatible status field for boards and date fields for calendar/timeline views. Formulas use a bounded postfix grammar, for example `$hours 2 *`; they do not execute PHP or JavaScript. Field edits must preserve existing valid records.

## Meetings and decisions

Create a meeting with attendees, agenda and minutes. Record its action items as assigned tasks. A resolution names its eligible voters and quorum explicitly. Each eligible person records one vote under their own identity. Closing calculates and freezes the result.

Recorded decisions and votes remain historical evidence. Use **Create correction** to link a new decision to the original. Implementation progress is a separate record and does not rewrite the ballot. Audit corrections append explanatory events.

## Export, import and backup

The portability view exports the content you may currently read as JSON, CSV, Markdown or ICS. Continue exporting pages until the interface reports completion. JSON is the structured interchange format; Markdown is useful for documents, ICS for calendar exchange. Use the browser's print/save-PDF action for a readable copy.

Preview an import before confirming it. Imported objects become private drafts with new identities; old assignments, access grants and votes are not transferred. Referenced objects must be included in the same reviewed batch. Import previews accept up to 100 objects and a 1 MiB manifest. Confirmed batches accept up to 7.1 MB including encoded attachment bytes; each file remains limited to 5 MiB. These request bounds protect the server and do not limit stored document counts.

Content export is not a full backup. Download private attachments separately and include their exact bytes when restoring a structured file object. For complete recovery, back up the WordPress database together with plugins and site files. Test the restore in an isolated installation before relying on it. Keep the prior official plugin ZIP for software rollback; a database restore is a separate operation.

The privacy view exports the current user's personal data and offers an explicit private-content erasure workflow. Review the confirmation carefully. Erasure can retain empty structural markers needed by other people's content. Shared records and audit evidence are not silently rewritten.

## Work through MCP

Install Codaroq MCP Core 1.6.3 or newer alongside Workspace and connect a compatible client to your site's existing Core endpoint. Ordinary members may explicitly authorize Workspace-only scopes. Existing tokens are not automatically expanded.

Choose `workspace.read`, `workspace.write` and, where required, `workspace.manage`. The token scope and the current workspace/object permission must both allow an action. Use tool discovery for the exact current schemas.

For example, discover `workspace.list`, read a selected workspace and create meeting minutes with `workspace.meeting.create`. Create assigned actions with `workspace.task.create`, then use `workspace.resolution.create`, `.vote` and `.close` for an explicitly eligible ballot. Every write needs a stable `request_key` of 16–64 letters, digits, underscores or hyphens. Retry the same business request with the same key. Supply the object's current `version` when changing it.

The authenticated Workspace REST interface permits up to 600 reads and 120 commands per minute per user, independently of MCP Core. A structured HTTP429 response reports how long to wait. These request safeguards do not limit stored users or documents. MCP also uses Core transport protections.

Follow list cursors. Where returned, retain `resource_version` as `if_version` on subsequent pages; restart the listing after a conflict. File downloads require `workspace.file.download`. No MCP tool grants an administrator exception to private data.

## Official updates

The Workspace updater verifies signed release metadata and the downloaded package digest through the official Codaroq channel. A licence is not required. Before a production update, take a current backup and retain the installed version's ZIP. Afterward, verify the installed version, real content and your client's MCP tools.

## Deutsch: erster Arbeitsablauf

Öffnen Sie **Workspace**, erstellen Sie einen Arbeitsbereich und laden Sie bestehende WordPress-Mitglieder unter **Team** ein. Legen Sie Seiten, Aufgaben und Sitzungen an. Wählen Sie für jeden Eintrag bewusst **Privat**, **Geteilt** oder einzelne Freigaben. Übergeordnete private Seiten bleiben auch für deren Anhänge massgeblich.

Ein Beschluss benötigt ausdrücklich festgelegte Stimmberechtigte und ein Quorum. Erfasste Stimmen bleiben erhalten; eine Korrektur ist ein neuer, verknüpfter Beschluss. Der Umsetzungsstand ändert das festgestellte Ergebnis nicht.

Exportieren Sie alle benötigten Seiten und laden Sie private Dateien separat herunter. Prüfen Sie jeden Import, bevor private Entwürfe angelegt werden. Eine vollständige Wiederherstellung benötigt zusätzlich eine geprüfte Datenbanksicherung. Vor einem Live-Update: aktuelle Sicherung, altes ZIP aufbewahren und anschliessend Oberfläche, Inhalte und MCP erneut prüfen.

Personal privacy exports include only your own objects that remain accessible under current membership and object permissions. File content is excluded and protected linked objects are redacted. Native WordPress exports restore the operator's original user context after processing.

Persoenliche Datenschutzexporte enthalten nur eigene Objekte, auf die die aktuellen Mitgliedschafts- und Objektrechte weiterhin Zugriff erlauben. Dateiinhalte werden ausgeschlossen und geschuetzte Verknuepfungen verborgen.

Search, calendar ranges and database filters evaluate only accessible content. Continuation cursors never count private matches. Search also respects redacted linked content. Database views preserve global ordering over the authorized population before pagination.