Admin
Manages the team, roles and every list. Built in and not editable.
Every listTeamRolesOrganisation fields
The workspace, screen by screen
Chat is where you ask. The lists, record forms, approvals and activity trail are where the work happens. The lists and forms are generated from one 186-module ERP model, so the conversation, the record and the trail agree.
01 · Ask
One question, answered with the records behind it
Ask in business language — which orders will miss their dates this week? The agent lists its areas, searches only the records your role can read, and shows each step as a plain-language card. When the question crosses into another agent's area, Chief hands it over and brings back one answer.
- 12 agents: Chief coordinates, each specialist owns its own lists.
- Tool cards name the list, the count and the filters. Field keys and ids stay out of the conversation.
- Module scope and role checks run on the server for every read, not just in the screen.
agent workspace · Sales
Which sales orders will miss their promised date this week?
looked at sales orders · 23 records
read delivery dates · 2 at risk
S
Sales · just now
Two orders will miss their promised date: SO-0012 due Tuesday and SO-0019 due Friday. Both hold the same backordered line, so I asked Chief to check the supplier date with Supply Chain.
Handoff
Confirm the supplier date for the 16 A line before we promise a new date.
Representative preview of the agent workspace
02 · Approve
A change that matters stops for a person
Stage moves, amounts above a configured threshold and writes to connected apps arrive as a proposal inside the conversation: a plain-language summary of what will change, with approve and reject. The reason and the decision are recorded in Activity. Approve or reject; the card then says what happened. If your role cannot perform the operation, the approval is refused.
- Transitions are approval-gated in most lists; 60 lists hold creates or updates above a threshold.
- Deletes are denied by default in 166 lists.
- Nothing in a held change is written until a permitted person approves.
conversation · DealsWaiting
S
Sales · just now
The update is prepared. It needs your approval because the amount is above the threshold for Deals.
Needs your go-ahead
WaitingChange a record in Deals — Amount: 48,200, Expected close: 30 Nov, Owner: Priya Rao
Nothing was saved yet.
The request and its reason are kept in Activity
ApproveReject
Representative preview of a held change
03 · Work the lists
The lists are the business, grouped the way you think
Work opens the lists your role can see — directories, pipeline, money and tax, supply, projects and the rest — grouped into sections instead of a wall of tables. Each list is a real module. The workspace contains 186 modules with 3,181 fields and 1,934 relations between them.
- Sectioned, tabbed forms: Overview, Financials, Details, Relationships and Settings.
- Line items, computed totals, related-record links and generated references such as SO-0012.
- Setup lists are read-only for non-admins; child records open from their parent rather than as another menu row.
SO-0012 · Sales order
Northbeam Electrical
updated 10:42
OverviewFinancialsDetailsRelationships
Customer
CompanyNorthbeam Electrical
ContactM. Okafor
OwnerPriya Rao
Lines
3 items
16 A distribution board×412,800
Cable tray · 3 m×122,160
Install kit×1640
Convert to invoice
Representative preview of a sales order
04 · Bring your data
A file in, a reviewed import out
Choose the list, upload CSV, TSV, JSON or TXT, and check the mapping before anything is saved. SynqTools scores each column against the model, marks how confident it is, runs a dry check with row-level errors, then imports only what you confirm.
- Suggested mapping with a confidence word for every column; each one is editable.
- The dry run reports ready and failed rows; skipped rows are listed after import.
- Import jobs and row counts appear in Workspace; Activity records that the import happened.
workspace · bring in your dataDry run
1 Upload→2 Map columns→3 Check→4 Import
leads.csv
214 rows · target: Leads
Company nameEnterprise namesure
Contact nameNamelikely
PhoneMobile phonelikely
SourceSourceunsure
NotesSkipped—
208 ready · 6 rows need attention
no records imported yet
Import 208 records6 skipped rows stay listed
Representative preview of a file import
05 · Connected apps
Apps your agents can use, with the door only where you opened it
An admin connects a business app once, then grants an agent the actions it may use — one action, a family, or all of them. Read-only actions run inline and are logged. Anything that changes the external app waits for an admin approval. App sign-ins stay with the connector service, not this workspace.
- Per-agent grants by action pattern, not one blanket token for the whole crew.
- 60 common read actions already run inline.
- Every agent-initiated connector run is recorded in Activity.
Connected apps · Agent accessAdmin only
Grant access
Choose an agent and an account, then limit the app actions it can run.
AgentAppAllowed actions
Sales agentGmailsearch, read, send
Sales agentGitHubget_issue, search_issues
Finance agent—no app granted
Reads run inline and are logged. Anything that changes the app waits for an admin. App sign-ins stay with the connector service.
Representative preview of an agent grant
06 · Prove it
The trail is written as the work happens
Agent searches, held changes, approvals, handoffs, imports, stage moves and conversions land in Activity in business words — Looked at, Changed, Converted, Not allowed, Waiting for you. Admins see the organisation and can filter by teammate; everyone else sees their own.
- Admins filter by teammate; non-admins see only their own activity.
- Agent searches, refusals and held changes are recorded; direct record edits and team changes are not part of this trail.
- The trail lives in the workspace; it is not a CSV you have to assemble.
Activity · Northbeam IndustrialEveryone · Me
WhenWhoWhatWhereResult
10:42Priya RaoConvertedSales ordersDone
10:38SalesLooked atSales ordersDone
10:06Sam LeeImportedLeadsDone
09:51SalesChangedDealsWaiting
09:12FinanceDeletedInvoicesNot allowed
Representative preview of the activity trail
07 · People and roles
Give each person the lists their job needs
Invite teammates by email, give each a role, and adjust access list by list. The built-in Admin role manages the team and every list; the Member role works every list but cannot change setup lists. Custom roles can be view-only for one list and full for another.
- Invitations are single-use and expire after seven days.
- Read, create, update and delete are set per list; an agent appears only when one of its lists is readable.
- Admins add an organisation field once; it appears in forms, imports and the agent’s answers, and its values follow each list’s update permission.
Member
Works every list, but cannot change setup lists or the organisation.
Work listsNo setup writes
Support
An example custom role: read-only on Service and Customers & suppliers.
View ServiceView Customers
Representative role setup; access is checked on the server, not just hidden in the UI
Start here
Start with your own workspace
Create a workspace, invite the people who own the work and ask Chief for the first real answer. If you would rather see it against your own process first, book a walkthrough.