The AI gets no master key. Only the permissions of the person asking.
The context of your work lives in systems like ERP, CRM, SharePoint or Outlook. There, neuland.ai HUB reads only what the person asking, or their group, may read, and writes only after approval.
Library
Ready-made connectors for common systems. Everything else via API, MCP or database.
Connectors for Microsoft 365, Atlassian, CRM and file storage, for example, are ready to use. Whatever is missing, neuland.ai HUB reaches via REST API, MCP or the database.
Microsoft Outlook
Office & collaboration
Reads email and calendars, creates events, sends after preview and confirmation.
Microsoft SharePoint
DMS & storage
Uses folders as a knowledge source; permissions stay with Microsoft.
Microsoft OneDrive
DMS & storage
Searches shared files and folders as a knowledge source.
Microsoft Teams
Communication
Posts in channels, links files from OneDrive and SharePoint.
Jira
IT & development
Reads tickets, links and projects, and answers users' questions about them.
Confluence
IT & development
Searches pages and spaces as a verified knowledge source.
HubSpot
CRM
Reads contacts, companies, deals and history for the chat.
Salesforce CRM
CRM
Brings in contacts, opportunities and history from the CRM.
Fireflies.ai
Communication
Pulls meeting transcripts into orchestrations.
Nextcloud
DMS & storage
Uses your own folders as a knowledge source, on-premises too.
GitHub
IT & development
Searches repositories, issues and pull requests.
SAP S/4HANA
ERP
Reads master data and business documents from your core ERP system.
One account
From admin approval to a fixed workflow. Each person connects their account only once.
Using purchasing as an example: four steps from approval for the group to the check that runs on schedule every Friday.
Permissions per connector
Reading needs no OK. Writing does.
neuland.ai HUB fetches the promotion plan, stock and shipping notice without asking. The notice to 20 stores in Teams and the follow-up with the supplier only go out once Purchasing approves. What a connector may do is defined per system:
- Permissions from the source systemIf a person can't open something in Microsoft 365, Jira or the CRM, the AI can't open it either.
- Writing only after an OKNotices in Teams, emails and calendar events wait as drafts until Purchasing approves.
Example: Purchasing
One agent queries three systems. And drafts the notice to 20 stores.
The buyer starts the promotional stock agent. It fetches the promotion plan, stock and shipping notice and drafts the notice to the stores; it goes out only once she approves.
Fachmarkt GmbH
Task: Do we have enough promotional stock this week?
Read this week's promotion plan
Queried stock for item 40771
Found shipping notice
Calculated allocation
Notice to 20 store managers
Notice sent to 20 store managers.
Every access uses the buyer's permissions: in Microsoft 365 through her account, in the inventory system through the permissions of the Purchasing group.
Access per system
Accounts per person, databases per group. And every access is in the log.
Store management asks for its allocation and gets it. The purchase prices sit in the same inventory system, enabled only for Purchasing.
Your own systems
Your ERP doesn't have to be new. Just reachable.
If the data is in an SQL database, the neuland.ai HUB queries it directly, like the stock in merchandise management. We connect systems such as ERP, DMS, PPS, SCM or your own specialist applications individually as an additional service, including legacy systems.
- Custom integrationEven a POS system without a modern API gets an interface; Customer Success schedules it in the onboarding plan.
- Your own MCP serversMCP is an open standard that AI applications use to call tools. With your own MCP server, neuland.ai HUB also reaches your internal tools.
- REST APIYour own applications and systems talk to neuland.ai HUB through its REST API.
FAQ
What a connector can and cannot do.
Yes, in Outlook, Teams, Jira, Confluence, HubSpot, Salesforce CRM and Microsoft Entra ID, but only with a human OK. Read steps run freely; write actions such as emails, events, tickets, posts or group changes wait until someone approves. Where a person has connected their account, neuland.ai HUB can never do more there than they can.
Yes, once. After that, neuland.ai HUB works with this account in every chat, every agent and every orchestration, with exactly the permissions the person has in Microsoft 365.
Yes. We connect systems such as ERP, DMS or specialist applications individually as an additional service, including legacy systems. If the data is in an SQL database, the ready-made SQL connector is often enough; the neuland.ai HUB also reaches your own tools via MCP servers.
A REST API for your applications, with API keys that admins issue; usage shows up in the consumption report. There are also typed SDKs for Python and Node; see the overview at SDK and API documentation.
Ready-made connectors need no development project: once a connector is available for the group, everyone connects their account once and gets to work. Our Customer Success team plans custom integrations of systems such as ERP or business applications in the onboarding plan.
Including Outlook, Teams, SharePoint, OneDrive, Jira, Confluence, GitHub, Nextcloud, HubSpot, Salesforce CRM, Fireflies.ai and SQL databases. neuland.ai HUB reaches everything else via REST API, MCP or the database.
No. If a person can't open something in Microsoft 365, Jira or the CRM, the AI can't open it either. You keep managing permissions in the source system.
Yes. Every access appears in the history with arguments, response and duration, and can be exported.
Yes. MCP is an open standard that AI applications use to call tools. With your own MCP server, neuland.ai HUB also reaches your internal tools, enabled per person.
Your system list is enough. We'll show you how it connects.
ERP, CRM, file storage, mailboxes and much more, including the legacy system nobody likes to talk about.
After your request
- 01You send us the list of your systems
- 02We mark each system: ready-made connector, SQL query or custom interface
- 03You know what works right away and what needs a custom integration