A workspace you can create today
Sign-up creates the organisation, its Admin role and the workspace. It opens with the full 186-module model and no sample records; invites are single-use and expire after seven days.
What is in the agent workspace today
These notes describe capabilities implemented in the current codebase. We do not publish filler posts or projected metrics.
Chief now coordinates the specialist crew
Chief can hand a request to the right specialist, receive the answer and return one recommendation. Handoffs are one hop, visible in the thread and checked against the signed-in person’s list access.
Approval cards live in the conversation
A held change shows a plain-language summary of what will change, with approve and reject. Approving re-checks the person’s permission; nothing in a held change is written until a permitted person decides.
Record forms are sectioned and tabbed
ERP metadata drives broad tabs and semantic sections, so long forms no longer arrive as a field dump. Required fields, defaults, generated references and related records are visible before save.
Configured actions use in-app dialogs
Seven conversions and guarded stage moves collect required inputs, show confirmation copy and validate choices before the API executes anything.
Imports are reviewed before they land
Column mapping is suggested with a confidence word, then a dry run reports ready and failed rows; skipped rows are listed after import. The import is insert-only and no records land until you confirm.
Connector access is explicit and logged
Admins can connect third-party apps and grant specific actions to agents. Read-only actions run inline; anything that changes the outside app waits for an admin, and every agent-initiated run reaches Activity.
Activity is scoped to the person
Non-admins see their own activity. Admins can view the organisation and filter by teammate. Agent searches, refusals and held changes are recorded, not just successful writes.
Exports use the words on screen
Every list exports to CSV with business headers, only the populated columns and the current search applied. Exports are capped at 10,000 rows and follow the same read permission as the list.
Organisation fields are admin-managed
Only admins can add or remove organisation fields; values follow each list’s update permission and are enforced on the server. Fields appear in forms, imports and agent answers.
Next review
The next review will cover onboarding with a customer's real list set, connector actions beyond the current inline read-only allowlist (write actions already require admin approval), and the first customer references once we have permission to publish them.
Start here
Ask about a capability
If a note matters to your operation, ask for a walkthrough focused on that workflow.