
3DEXPERIENCE implementation and configuration
We configure collaborative spaces, organisations and roles around how engineering creates, reviews and releases data. Then we test who can read, revise and change maturity in each security context, and document the settings your administrators will maintain.
Problems this covers
- A new 3DEXPERIENCE platform needs configuring before real projects start
- Collaborative spaces and roles have grown messy and nobody is sure who can do what
- Maturity states and approvals don't match the release process engineering actually follows
- Change Actions and Routes are set up but people work around them
- Rolling out to a new site, team or business unit
- Your partner needs capacity on configuration and testing

From access design to an accepted release workflow
Map the process
How data is created, reviewed, released and changed, by whom, and which ENOVIA apps and roles are installed.
Design access
Collaborative spaces, organisations, roles and policies, written as a matrix your administrators can read.
Configure and test
In a test environment first. Test scripts cover allowed actions, refused actions and rejected approvals, with representative users.
Roll out
Support for users and administrators in the first weeks, and handover notes.
What you receive
- An access matrix: collaborative spaces, roles and what each can do
- Configured maturity states, Change Actions and Routes where your roles provide them
- Test scripts and recorded results, including refused actions
- Administrator handover notes and rollout support for an agreed period
Three ways to start
Start with free support
Up to 5 hours to understand the issue and tell you what to check or do next. No obligation.
Request free supportEssentials assessment Paid
A written problem statement, recommended next steps, a proposed scope and an effort estimate. You approve the fee before it starts.
Ask about an assessmentDiscuss a scoped project
Upgrade, migration, integration, customisation or configuration with a defined goal. We reply with questions, then a proposal.
Discuss a projectWhat to include in your first message
- Cloud or customer-managed, release and FD
- Installed ENOVIA apps and roles, if known
- Number of users, sites and collaborative spaces in scope
- The process to configure first (release, change, approval)
- Target date, and whether a Dassault Systèmes partner is involved
A few lines are enough. Please leave out passwords, confidential CAD files and customer data.
Common questions
Cloud or on-premise?
Both. What can be configured differs between the Dassault-managed cloud and customer-managed installations, so we confirm what your release, FD and roles allow first.
Do you sell 3DEXPERIENCE licences?
No. We're an independent services team. Licences and roles come from Dassault Systèmes or its partners.
Can you work under our partner's project?
Yes. We can deliver configuration and testing as a defined work package under a Dassault Systèmes partner's project lead.
Describe the failed operation, release and deployment.
Describe it in a few lines. If it's a good fit, we'll use up to 5 hours of free support to understand it and tell you plainly what to check or do next.