Multi-tenant
Each client lives in its own tenant — extracts, analyses and knowledge base stay strictly separate. Your user can be a member of several tenants: one login, many engagements, no mixing.
For consultants
One tool that scales with every client
Conjola is the product — you put it to work as a tool at your clients. Each client in its own tenant, role-based and strictly isolated: multiple engagements run in parallel with no data bleed. Once the extracts are in, the analysis is ready on the next business day — instead of after weeks of workshops.
Built for consulting firms
Multi-tenancy is not an add-on in Conjola, it is the foundation. That is exactly what sets it apart from project-bound, one-off solutions.
Roles & security
Role-based access and a login with mandatory two-factor authentication govern who sees what. Consultants and client stakeholders each get exactly the role they need.
Repeatability
A standardized routine from extract to knowledge base: the same transports, the same reports, the same preparation. What works at one client runs identically at the next.
From extract to client presentation
Four steps, every time the same — from raw SAP export to the steering committee meeting.
Get the tenant
We set up the client tenant at your request, at short notice. The client imports the Conjola transports, runs the reports and uploads the extracts — with nobody accessing their system.
Understand the landscape
Feature map, Feature Insights and transaction usage show, per company code and system, what is really used — without weeks of as-is workshops.
Analyze custom code
The AI describes every Z object, assigns it to the feature map via tables, transactions and function modules, and groups the rest by topic. You see what the custom code stands for and where it overlaps functionally.
Present & document
Walk the client through the analyses directly in Conjola. Functional specs grow in the knowledge base — the AI assistant proposes, you accept or discard.
Your edge in the pitch
You no longer argue from assumptions, but from the client's real data.
Facts over folklore
Every statement about the system landscape rests on the client's own data — real usage, analyzed custom code — traceable and verifiable by the client.
Faster to proposal
Instead of weeks for the as-is capture: once the extracts are in, the analysis is ready on the next business day. That shortens lead time and makes fixed-price scoping more reliable.
Differentiation
A repeatable, data-driven method sets your firm apart from competitors still working with spreadsheets and interviews.
And when your developers work with AI
MCP access opens the feature map, custom developments and knowledge base to Claude Code and other MCP-capable clients such as Codex CLI or Copilot — read-only and with the same tenant isolation as the UI.
One access per project directory
Every token is bound to exactly one tenant and one landscape. Keep the MCP configuration in each project directory, and the agent in client A's project sees client A only — “compare with client B” simply has no data to work with there. The separation applies exactly where your duty towards your clients does.
A token belongs to a person
No service account with nobody behind it: issuing, revoking and every release of source code sit in the tenant audit log with a user attached. Who had access when stays provable.
The client decides about their code
Whether source code may leave through the access is the tenant's own switch, separate from enabling it. One conversation you have up front instead of an assumption you explain later.
See MCP access →
How a transformation project runs with Conjola →
Ready to understand your SAP landscape?
In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo