Integrator in practice: connecting a customer

Result first: Kranvik Precision is integrated

Hello and welcome to the PaperOffice AI Academy. Episode four of the partner series is about working as an integrator in practice: we connect a customer technically. First, the result. For our customer Kranvik Precision in London, there is a dedicated Workspace in our account. Their invoices arrive there automatically from their mailbox, and their team asks questions about the documents in Claude without seeing anything else in our account. This is achieved in four steps: a Workspace for the customer, a user group with exactly this Workspace, a group token for Claude, and the automatic receipt of documents. Finally, we will see where the usage ends up.

Chapter 1: One Workspace per customer

As an integrator, your solution runs on your own PaperOffice account. Your customer pays you at your price, and your usage receives the integrator benefit. For each customer, create a dedicated Workspace. This ensures that documents, agents, and knowledge remain separated per customer. We refer to it as Kranvik Precision.

Chapter 2: A group with exactly this Workspace

To ensure that your customer’s team only sees their Workspace, create a group under User Groups. When configuring the Workspace Access, select the whitelist and assign only Kranvik Precision to it. For this Workspace, you define what the group is allowed to do with the documents, such as viewing and downloading, but not uploading. Set areas like Storage Mounts or Connectors to “No access”. A common mistake is a group with full access. Then the token sees all Workspaces in your account, including those of your other customers. So check in the group list that access is restricted.

Chapter 3: A group token for Claude

Under API & Developer, you now create a group token for this group. It is meant for MCP Connect, that is for Claude, ChatGPT or Cursor, and takes on exactly the rights and Workspaces of the group. You can copy the token at any time from the list of API Keys. Treat it like a password and share it only via secure channels. In Claude, your customer adds PaperOffice as a connector and logs in once, using the token. From then on, their team queries their own documents directly in Claude. For server processes, on the other hand, you use an API key. For Claude and other AI assistants, there is the group token or the user token. If someone leaves your customer’s team, rotate the token. The app immediately generates a new one, and the old one becomes invalid. Your customer enters the new one into Claude once.

Chapter 4: The documents arrive automatically

Now the documents arrive on their own. The easiest way is the customer’s invoice mailbox: under Storage Mounts, you connect the mailbox via IMAP, with the username and an app password. A Connector in import mode retrieves new emails at fixed intervals and stores them in the Workspace Kranvik Precision. There, PaperOffice reads the documents just like any other document. If your customer has a NAS or a scanner, connect it using the same method, for example via SFTP. Dedicated videos on this topic are available in the Academy.

Chapter 5: Custom workflows with n8n

For your own processes, use the API, for example with n8n: New invoices are extracted, checked, and forwarded. Our film “The inbox that thinks along with you” in the Academy shows you how to build such an inbox step by step.

Chapter 6: Where the usage ends up

All calls are processed through your account. You can see your integrator benefit on the partner badge on your plan card and on each line under API usage. What you charge your customer for this is up to you. In summary: one Workspace per customer, a group containing exactly this Workspace, a group token for Claude, and the documents arrive automatically via mailbox or NAS. Everything runs through your account. The next and final episode is about working as a reseller in practice: how your customer gets started on their own. Until next time in the PaperOffice AI Academy.