Governance

Governance, security, and control by design.

MagiSuite is built for governed operations: controlled access, full traceability, and deployment models aligned to your constraints.

The trust architecture

How control works, in 5 layers.

From infrastructure perimeter to user role, each layer adds a clear and verifiable control.

From infrastructure perimeter to user role, each layer adds a clear and verifiable control.
  1. Layer01Where it runs

    Choose SaaS, self-hosted, or dedicated based on regulatory and operational constraints.

  2. Layer02Where you test

    Keep dev, test, and production separated with controlled promotions across environments.

  3. Layer03What you trace

    Every action records actor, timestamp, and outcome for full auditability.

  4. Layer04Who can act

    Define granular permissions by action and scoped visibility by team.

  5. Layer05Who is accountable

    Assign roles and responsibilities with centralised identity, SSO, and MFA.

  6. Core

    Operations

    Controlled by design

Access control

Define who can view, change, and approve.

Configure roles, permissions, and visibility rules by operational context. SSO and MFA provide centralised, verifiable access.

  • Role-based access control (RBAC)
  • Integrated SSO and MFA
  • Granular permissions per action
  • Visibility by team, function, and role
  • Centralised user and group governance
Role \ ActionViewEditApproveExecute
Admin
Manager
User
AllowedPartialRestricted

Identity lane

  1. UserAuthentication required
  2. Identity ProviderSSO + MFA verified
  3. MagiSuiteAuthorised session

Centralised identity with SSO + MFA before each session.

Audit trail

Make every decision auditable.

Events, changes, approvals, and process steps stay traceable to monitor, reconstruct, and audit each operational flow.

Events, changes, approvals, and process steps stay traceable to monitor, reconstruct, and audit each operational flow.
Audit log· Last 24 hours
  1. 08:14Maria RossiCreated

    Created purchase request

    Order #PO-2031MagiFlow

  2. 09:02Luca BianchiReviewed

    Supplier and payment terms verified

    Order #PO-2031MagiTable

  3. 10:47Elena ContiApproved

    Manager sign-off above spend threshold

    Order #PO-2031MagiFlow

  4. 12:18MagiAIUpdated

    Delivery date updated on request

    Order #PO-2031MagiAI

  5. 14:35SystemNotified

    Threshold exceeded, escalated to owner

    Order #PO-2107Rule

  6. 17:32SystemCompleted

    Outcome archived and audit entry signed

    Order #PO-2031MagiSuite

5 canonical steps · exportable · signed for integrity.

Operational continuity

Operational continuity without compromise.

Separated environments, scheduled backups, and tested recovery procedures reduce operational risk.

Separated environments, scheduled backups, and tested recovery procedures reduce operational risk.

Environments pipeline

  1. Dev
    env · 01
  2. Test
    env · 02
  3. Prod
    env · 03

Operating practices

  • BackupScheduled
    retention

    Scheduled snapshots with configurable retention.

  • RecoveryTested
    runbook

    Documented, periodically tested restore procedures.

  • MonitoringActive

    Continuous observability on service health and performance.

Deployment models

Choose the deployment model that fits.

Each model addresses different infrastructure, governance, and compliance needs.

  • SaaS

    Ready-to-use cloud environment to move faster with lower infrastructure complexity.

    • Managed by Soolve
    • Faster onboarding
    • Shared infrastructure
  • Self-hosted

    Deployment in your infrastructure for full control over network, configuration, and data.

    • Your infrastructure
    • Full configuration
    • Local data residency
  • Dedicated

    Isolated environment for strict separation, scalability, or governance requirements.

    • Isolated tenancy
    • Custom scaling
    • Specific governance

Reference frameworks

Designed on recognised principles.

Quality, information security, operational resilience, traceability, and access control are native design principles.

  • Quality

    ISO 9001

    Approach inspired by quality management system principles.

    Design reference

  • Information security

    ISO/IEC 27001

    Roles, processes, and controls modelled on recognised information security practices.

    Design reference

  • Cyber resilience

    NIS2

    Attention to governance, risk, and technical measures aligned with evolving requirements.

    Design reference

These are design references, not formal compliance statements.

Move faster without losing control.

Share your governance and deployment requirements: we define the model that best fits your context.