Set up a company
A workspace holds one organisation’s ledgers, people, agents and rules. Agents post journals through the Koncernify gateway, so the workspace decides what each agent may post and who has to approve it. The steps below are carried out once by an owner.
1. Create the workspace
Sign in to the app with a Google or Microsoft work account and name the workspace. The person who creates it becomes its owner. A new workspace has a 14-day trial, during which every feature is available.
2. Connect the ledgers
Each company’s books are one ledger. Under Settings, Ledgers, add a ledger for each company. A Fortnox company is connected by signing in to Fortnox (see Fortnox). The server stores these credentials encrypted and uses them only when it posts or reads on someone’s behalf. No agent or assistant holds the ledger’s credentials.
3. Invite people
Under Settings, People, invite colleagues by the email address they sign in with, and give each one a role.
| Role | What it allows |
|---|---|
| Owner | Everything, including people, ledgers and billing |
| Controller | Approving journals, the rules, agents, reports and auditor links |
| Accountant | Drafting journals, approving other people’s within their authority, and reading reports |
| Auditor | Reading the review queue, the records and the reports |
A person’s authority narrows what they may approve. It can set an amount limit, the accounts they cover (codes or the start of codes) and the ledgers they cover. A journal outside someone’s authority waits for a person whose authority covers it.
4. Register the agents
Under Settings, Agents, register each agent that posts journals. The registration states whom the agent works for and its scope: the ledgers it may use, the accounts it may post to, the largest journal it may post, and an auto-post limit below which its journals post without review. The key is shown once, together with the settings the agent needs.
The person an agent works for cannot approve that agent’s journals. Separation of duties holds for every registered agent, whatever the workspace’s rules say.
5. Connect the agent
On the machine where the agent runs, add the gateway to .mcp.json:
{"mcpServers": {"scopegate": {
"command": "Koncernify", "args": ["books", "gateway-mcp", "--entity", "ent_..."],
"env": {"SCOPEGATE_URL": "https://app.koncernify.com", "SCOPEGATE_KEY": "sg_agent_..."}}}}The gateway offers three tools: post_journal, list_journals and list_accounts. A journal inside the agent’s scope and below its auto-post limit is posted at once. Any other journal waits in the review queue, and Koncernify posts it when a reviewer approves it, so the agent makes no second call. When the reviewer changes a journal, Koncernify posts the approved version. An agent that sends the journal again is told what was posted, and nothing is posted twice. Every posted journal carries its reference as [sg:…] in the narration.
An approved journal that the ledger refuses stays approved and is shown on the Review screen with the ledger’s reason. A reviewer either posts it again once the cause is fixed or sets it aside with a reason, which Koncernify signs. The month cannot be locked while an approved journal is neither in the ledger nor set aside, and the report names any such journal.
Once a workspace has a ledger, the hook refuses journals written to the ledger by any other route, and points the agent to the gateway.
The gateway keeps the agent’s books record on the agent’s machine, in ~/.scopegate/books.jsonl (or in SCOPEGATE_DIR). For each journal, it records the draft, the reviewer’s signed decision and the posting, under the reference the journal carries in the ledger. The service countersigns each change, so the record cannot later be rewritten unnoticed. The record holds the agent’s comment on each journal. The conversation that led to it stays with the agent.
6. Review and report
Reviewers approve, change or reject journals under Review, and the service signs each decision. Under Reports, pick a ledger and a month and choose Make report. The report compares the signed decisions with the ledger and can be shared with the auditor as a read-only link (see Reports and auditor links).
7. Read the books
The Books tab shows every entry in each connected ledger for a month and who made it. It is rebuilt every night, and Build now reads the ledger at once. Owners, controllers and auditors can open it. The times are set by the server and the decisions are signed, so the view can be checked against the record.
8. Billing
The plan is priced per connected ledger. An owner subscribes under Billing before the trial ends. After the trial, the review queue and the reports stay readable and nothing new is posted until the workspace subscribes.