Role-Based Security for SharePoint — Enforced by Dynamics 365.

Role-Based Security for SharePoint — Enforced by Dynamics 365.

Change a role once in Dynamics 365. SharePoint follows, and you can show it when someone asks.

Change a role once in Dynamics 365. SharePoint follows, and you can show it when someone asks.

Role-Based Security

Document Compliance

Built for CIO, CTO, and compliance teams

Three Non-Negotiables

01

Continuous by default

Security should be continuous, not a quarterly review. Access follows the role.

02

Compliance out of the box

Compliance evidence should be a by-product, not a standing remediation project. Ready whenever you are asked.

03

Performance scales with your business. Not your workload.

No backlog. No redundant reviews. No manual overhead. Every permission change is carried through, the most important first, whether you have ten users or ten thousand.

NIS2 Article 20
€10M
or 2% of global annual turnover, whichever is higher, for essential entities.
NIS2 Directive, Art. 20, 21, 32 and 34 · Applies as transposed into national law

Management is personally liable.
Not just the company.

Under NIS2 Article 20, management bodies, not just the organisation, can be held liable for cybersecurity failures. A stale SharePoint permission that exposes a confidential file is an access control failure. It is documented. It is auditable. It is your responsibility.

✓
Management bodies must approve and oversee cybersecurity risk measures
✓
Members can be held liable for non-compliance
✓
For essential entities, authorities may temporarily prohibit individuals from managerial roles

Permissions

Permissions follow roles

Permissions follow roles

Compliance

Evidence on demand

Evidence on demand

Regulatory

Supports alignment with NIS2, ISO 27001 and GDPR

Supports alignment with NIS2, ISO 27001 and GDPR

Microsoft Partner

Microsoft Partner

AI Risk

Your Permission Gap Is Now a Copilot Data Leak.

Microsoft Copilot works from every SharePoint file your users can access, including files they should no longer reach. When D365 revokes access but SharePoint permissions stay behind, Copilot can surface confidential documents to people who changed role, the wrong teams and expired contractors.

Doclave keeps SharePoint access aligned with your D365 security model, so Copilot only reaches what each user is authorised to see today.

!
Copilot surfaces stale access
Copilot Chat and M365 search work from every SharePoint file a user account can reach, whether or not that access is still valid in D365.
!
Copilot cannot see your D365 roles
Copilot respects SharePoint permissions as they are. It cannot tell that a permission should have been removed when the role changed in D365.
!
An access control gap under NIS2
Confidential data surfaced through stale access is an access control gap, which NIS2 Article 21 requires you to manage.
✓
Doclave closes the Copilot exposure window
Every D365 change is carried through to SharePoint, so Copilot's reach follows current authorisation.

Connect

Connect

Map Roles

Map Roles

Keep in Sync

Keep in Sync

Audit & Report

Audit & Report

Simple, Transparent Pricing

Simple, Transparent Pricing

Start Before the Audit

Start Before the Audit

Proactively secure SharePoint permissions

Proactively secure SharePoint permissions

© 2026 Doclave ApS · CVR 46721012 · Fynsgade 30A, 7400 Herning, Denmark · contact@doclave.com

© 2026 Doclave ApS · CVR 46721012 · Fynsgade 30A, 7400 Herning, Denmark · contact@doclave.com

© 2026 Doclave ApS · CVR 46721012 · Fynsgade 30A, 7400 Herning, Denmark · contact@doclave.com