Integrations
Connect Doconio with Microsoft 365 and your business systems.
Employees can sign in with Microsoft Entra ID, bring selected SharePoint documents into Doconio and connect agreed business systems. Start with the connection that removes the most manual handoffs from your evidence process.
Integration overview
Starting point
Your evidence workflow
Access
Roles and permissions
Microsoft identity for sign-in
Selected documents from SharePoint
Doconio actions for connected systems
Connection paths
Keep the Microsoft workspace familiar
Use Microsoft Entra ID for sign-in, select existing SharePoint documents and receive agreed Doconio notifications in Teams. Your teams keep familiar entry points while Doconio manages the evidence process.
Keep access clearly governed
People can only see the data and use the actions allowed by their Doconio role. A connected system does not create additional permissions, and decisions and relevant activity remain traceable.
Connect additional systems deliberately
Use the REST API to connect agreed business systems. Together, we define which data is exchanged and which process the connection should improve.
Connection paths
Choose the connection that fits your starting point.
Availability depends on the selected package and your requirements. In the product conversation, we clarify which connection creates useful relief and what is needed to introduce it.
Microsoft Entra ID
Let employees sign in with their existing Microsoft identity. Doconio roles continue to determine what each person can access.
SharePoint
Select an existing file and bring a specific version into Doconio for review, approval and traceability. Your team can continue working in SharePoint.
Microsoft Teams
Receive selected notifications and use agreed Doconio actions in Teams. The same Doconio permissions continue to apply.
REST API
Connect agreed business systems through the Doconio API. We provide the technical documentation needed for the agreed implementation.
Approach
How we plan the connection with you
Start from one concrete evidence process and the systems or people involved.
Agree which sign-in, document transfer or data exchange is required.
Configure only the access needed for the selected integration path.
Test sign-in, permissions, data flow and traceability with suitable examples.
Document the agreed scope and responsibilities before the connection is used.
Questions and answers
Integration FAQ
Which connections can we discuss today?
Microsoft Entra ID, SharePoint and the REST API are available with Enterprise. Selected Microsoft Teams functions can be discussed on request.
Does the SharePoint connection replace our document workspace?
No. Teams can continue working in SharePoint. Doconio takes over a selected, concrete document version when it becomes relevant for review, approval or evidence.
Do Teams users receive additional permissions?
No. The same Doconio identity and role permissions apply in Teams. The connection does not grant access to additional data or actions.
Which systems can be connected through the API?
That depends on the process and the data that needs to be exchanged. We clarify the target system and scope first, then provide the technical documentation required for implementation.
How much setup is required?
That depends on the selected connection and your environment. In the product conversation, we identify the involved systems, required contacts and a realistic introduction plan.
Next step
Start with one connection that removes real friction.
Tell us where sign-in, document transfer or system handoffs slow down your evidence process. We will identify the connection that provides the most useful relief.