Infrastructure control
Choose where the environment is hosted and establish who is responsible for the servers, network and storage underneath it.
DATA OWNERSHIP & CONTROL
Share the work.
Keep the control.
A collaborative environment should make information easier to use while keeping ownership, access and operational responsibility clear.
CONTROL IS A DESIGN DECISION
Think in layers, not promises.
Picowork’s platform architecture includes organisation-managed storage, workspace membership and file-level permissions. Their effectiveness depends on the selected configuration and how it is operated.
Participation control
Define who can enter a workspace, who can administer it and how external invitations are reviewed and removed.
Resource control
Review ownership and permitted actions for shared files. Distinguish workspace membership from access to individual resources.
FOLLOW THE INFORMATION
Four moments that deserve attention.
| Stage | Platform design | Deployment review |
|---|---|---|
| Access | Authentication and authorised entry into CoSpace | Confirm supported authentication options, identity checks and account lifecycle |
| Upload | Resource owners assign sharing permissions | Validate permitted actions for each content type and participant role |
| Open | Web applications operate within a sandbox model | Review isolation, application trust and supported browser behaviour |
| Store | Information can reside on organisation-controlled infrastructure | Agree storage location, retention, backup and recovery responsibilities |
LOCAL OWNERSHIP, CLEAR RESPONSIBILITY
Your data.
Your decisions.
Organisation-managed storage gives a team a basis for deciding where information resides and who operates the environment. It also makes operational responsibility explicit: someone must manage the infrastructure, protect access and prepare for recovery.
A shared workspace may also include external applications or linked resources. Those services can have their own storage and access behaviour. Review the complete data flow, not only the location of the Picowork host.
For cross-organisation collaboration, document the information being shared, the permitted actions and what happens when participation ends. The goal is a clear, repeatable model that users and administrators can both understand.
GOOD QUESTIONS. BETTER DESIGN.
A governance conversation worth having.
Who owns a workspace?+
Assign a responsible owner to each CoSpace. Define who may add members, change administration and decide how resources are organised. Ownership should continue when the original project lead changes role.
What happens when someone leaves?+
Review membership and application access together. Identify the resources that need handover and the retention requirements that apply. Validate the available removal and revocation behaviour rather than assuming that all external copies can be recalled.
How should external collaboration be approved?+
Set a process for approving outside participants and the material shared with them. Choose the minimum appropriate permissions and review those permissions when the purpose of collaboration changes.
Does private hosting automatically establish compliance?+
No. Hosting location is one part of a wider compliance and governance assessment. The organisation must assess its use case, information handling, configuration and operating practices against the requirements that apply to it.
Are security certifications or guarantees stated here?+
This website does not claim a current certification, independent audit result or security guarantee. Specific assurance requirements should be reviewed against current technical and contractual evidence.
What should a security review cover?+
Identity and authentication; network boundaries; application isolation; permissions; data flows; storage and recovery; operational monitoring; update responsibilities; and the handling of incidents. The review should match the planned deployment and its actual information sensitivity.
YOUR NEXT CHAPTER
Put control into your plan.
Start with the people, resources and infrastructure you already have. Build a clearer picture of what collaboration could become.
Build your collaboration brief