Core principle

MASTERINSOFT® is the single source of operational truth.
The Drive does not replace processes, pipelines or entities (clients, deals or projects).

All operational documents live inside MASTERINSOFT®, within their proper context, state and history.
The Drive exists as a transversal, institutional repository, structured, controlled and non-operational.

Tree-based structure without loss of control

The Drive structure is simple at the top level, while allowing the creation of subcategories and subfolders whenever needed, ensuring:

1. Intuitive tree-based navigation.

2. Faster and more accurate document location.

3. Logical organisation without unnecessary fragmentation.

Structural granularity is an organisational decision, not a technical constraint.
This ensures long-term stability while allowing flexibility where it genuinely improves usability.

Fine-grained access control

Each folder and document in the Drive supports granular access permissions, allowing organisations to:

1. Define read, edit or management rights by role, team or function.

2. Ensure that sensitive information is only accessible to authorised users.

3. Meet compliance, security and segregation-of-duties requirements.

Access is no longer generic — it becomes intentional, auditable and aligned with organisational governance.

Integrated document versioning

The MASTERINSOFT® Drive provides full document version management, allowing users to:

1. Upload new versions without losing previous ones.

2. Access and review historical versions at any time.

3. Maintain a clear and auditable evolution of each document.

There is no blind overwrite and no information loss.
Each document retains its complete lifecycle and history.

What the Drive must not contain

The Drive is not an operational workspace.
It must not contain:

1. Client contracts.

2. Deal-specific proposals.

3. Documents from active projects.

4. State-dependent files (for example: “under negotiation”, “approved”, “in progress”).

These belong to the process context inside MASTERINSOFT®, where state, automation and traceability are enforced.

What the Drive should contain

The Drive acts as a nearly static institutional repository, with a clear and sustainable structure.

Recommended top-level structure:

1. Institutional

2. General Finance

3. Human Resources – General

4. Sales & Marketing – Base

5. Product & Technology – Base Documentation

6. Quality, Compliance & Security

7. Templates

8. Historical Archive

Within each category, subfolders may be created whenever appropriate, without compromising the overall governance model.

Golden rule

If a document makes sense outside MASTERINSOFT®, it belongs in the Drive.
If it only makes sense within a process, it never goes to the Drive.

Direct benefits

1. Clear organisation with structural flexibility.

2. Strict control over information access.

3. Full and auditable document history.

4. Reduced security and compliance risks.

5. MASTERINSOFT® reinforced as the operational core of the organisation.

6. Faster, simpler and more consistent onboarding.