01 / 05 · CHOOSE SOURCES
SharePoint, OneDrive or Google Drive.
Your team maintains documents in its familiar storage. Together, we select the folders and documents Mikis should use for your tasks.
You define sources and access rules.
YOUR KNOWLEDGE IN MIKIS
Use existing data. Keep knowledge current.
Make your company knowledge available in Mikis. We connect selected documents from SharePoint, OneDrive and Google Drive, with automatic synchronisation on request.
CONNECT DATA · USE KNOWLEDGE
From SharePoint and Google Drive to your report.
One connected example: choose sources, keep knowledge current and prepare results with Mikis.
01
02 / 05 · KEEP KNOWLEDGE CURRENT
Keep up with document changes.
On request, we configure automatic synchronisation. New and updated documents are prepared for Mikis at agreed intervals.
Optional setup · Freshness depends on the last successful sync.
03 / 05 · QUESTIONS AND SOURCES
Ask questions. Get relevant sources.
“Which travel expense policy applies to our workshop?” Mikis finds relevant passages in approved documents. Connected business systems can add information such as current order status.
Review the answer and data freshness; check the sources.
04 / 05 · PREPARE RESULTS
Turn information into your report.
Project documents, internal guidance and available order data become a report draft using your template. Your team reviews the result and takes it forward.
Example: project status with outstanding issues and sources.
05 / 05 · APPROVE ACTIONS
You decide what happens next.
Send a report, change data or create a case in a business system: we configure these actions with explicitly agreed permissions and approvals.
Agree the scope of reading, drafting and execution.
Sources, permissions and updates in detail
SharePoint and OneDrive
Make internal policies, manuals and project documents from selected Microsoft 365 libraries available to Mikis. We agree supported sources and access with your IT team.
Example: “Which travel expense policy applies to our workshop?” Mikis finds relevant approved passages and cites its sources.
Google Drive
Use selected project folders and documents for questions, comparisons and drafts. Your team continues to work in its familiar file storage.
Example: prepare a status report with outstanding issues from a project brief and meeting notes.
Keep knowledge up to date
As an optional setup, we regularly synchronise selected knowledge sources. New and changed documents are processed according to the agreed procedure.
Example: a revised work instruction becomes available for new questions after the next successful sync.
With clear access rules
We define sources, user groups, update intervals and handling of deleted documents or revoked access. Existing permission mapping is checked for each integration.
Example: the service team uses approved manuals; personnel documents are outside this knowledge collection.
We configure the integration for your environment. Together, we define which folders are included, how often synchronisation runs and how changes, deletions and permissions are handled. Data flows and participating services are agreed with you in advance.
Which sources does your task need?
Documents
Find information in approved manuals, instructions and project documents.
Spreadsheets and databases
Compare and calculate figures using a verifiable data version.
Business applications
Retrieve only the information needed, using agreed access permissions.
Technical building blocks and availability
We select search, calculations and integrations to suit the task. Technical details are agreed with your IT team.
Before preparing a proposal, we clarify what is already available and which integrations need additional setup or development.
How far should the workflow go?
Read information
Start with restricted read access. Only agreed information is retrieved.
Prepare work
Bring information together and prepare a draft for your team to review.
Approve actions
Change data or send messages only with the agreed permissions and approvals.
Interface, automation or agent?
An interface connects systems. Automation follows defined steps. An agent can select the next steps within agreed boundaries.
What we check together before use
- Access, permitted fields, and read and write permissions.
- Typical questions, expected values and traceable calculations.
- Outdated or missing information and technical failures.
- For actions: approvals, logging and handling duplicate execution.
The agreed scope, test cases and responsibilities are recorded for your integration. Existing access and required new development are considered separately.
Confidential work in practice
Start with your security needs.
Recruitment agency
Pilot project · Confidential personal data
Why security made Mikis the right choice
View project →For power users and IT: terminal access and custom tools
FOR POWER USERS AND IT
Connect your own tools.
Terminal and technical workflows
For power users, developers and IT, approved tools and scripts can be made available through a separately configured terminal connection.
Example: analyse logs or run an agreed diagnostic workflow. Your team describes the task in the browser.
Business systems and actions
Read access, drafts and write actions each have an explicitly agreed scope.
Example: prepare a ticket draft with diagnostic notes and create it in the connected system after the required approval.
Your team does not need terminal skills for everyday Mikis use. Technical integrations are optional extensions for defined tasks.
YOUR INTEGRATION WITH MIKIS
Which connection would help your team?
Tell us about the task and your existing system. Together, we clarify the data needed, permitted access and the first step.