How Nebulas Managed Nextcloud makes responsibilities clear between company and provider

01

What changes for people working daily on Nextcloud

When people share documents, calendars, contacts, and identities in a single environment, knowing who manages what helps collaborators and internal customers find their way more easily. Nebulas Managed Nextcloud addresses this need by explicitly documenting architecture, administrative access, encryption, retention, and support, so collaborators and internal customers always know who to turn to.

02

How clarity on responsibilities is built

Steps

1. Nebulas documents architecture, data location, and service dependencies
2. Defines who manages administrative access, encryption, and retention
3. Tracks maintenance, updates, and support according to the agreed scope
4. Records every change in an updated responsibility matrix

03

What is needed before starting the service

Prerequisites

• An agreed scope covering architecture, compute, storage, network, and security
• An inventory of existing data and permissions to be migrated
• Shared continuity goals, such as RPO and RTO

04

A hypothetical case: sales team and IT team

Hypothesis: the sales team reports an inaccessible shared file. With a documented responsibility matrix based on the agreed scope, the team can check who manages administrative access, encryption, and support for that area, directing the request to the right person or provider.

05

What to check to maintain clarity over time

• The responsibility matrix reflects current architecture and dependencies
• Administrative access is documented and kept up to date
• Protected copies and restore checks are tracked
• Every change to the service is recorded and traceable

06

How Nebulas Managed Nextcloud structures responsibilities

The service can cover architecture, compute, database, storage, cache, network, access, updates, monitoring, capacity, backup, security, and support according to the scope agreed with the organization. Nebulas inventories data and permissions, plans tests and the move to production, verifies integrity and performance, and prepares people to work in the new environment. Architecture, data location, administrative access, encryption, retention, dependencies, maintenance, and support are documented with a responsibility matrix and traceable changes.

07

Practical sequence for adopting the responsibility matrix

Steps

1. Agree on the service scope: what Nebulas manages and what stays internal
2. Have existing data and permissions inventoried before migration
3. Verify integrity and performance during the move to production
4. Keep the responsibility matrix updated and accessible to the whole team
5. Periodically review tracked changes together with the provider

08

The next useful step

If collaborators and internal customers struggle to understand who resolves what in your cloud environment, the first step is to request a documented responsibility matrix, with architecture, access, and traceable changes as the basis for every future conversation.