SAV Inspector Deutsch
HomeA controlled workspace for shared SPSS SAV files.
SAV Inspector Teams

A controlled workspace for shared SPSS SAV files.

Teams adds the collaboration and governance layer that a local file cannot provide: organisations, projects, permissions, encrypted storage, named versions, comments and reviews around a concrete SAV file.

Make the valid file state explicit

Email attachments and shared folders make it difficult to tell which SAV file contains the approved labels, recodes or missing-value rules. Teams stores each deliberate save as an immutable version with author, time and optional comment.

A reviewer approves or rejects a specific version. A later change creates a new state instead of silently changing the already reviewed file.

Access follows the research project

Organisations contain projects and members. Server-side checks decide who may list, open, version or review a dataset; hiding a button in the browser is not treated as an access control.

  • Organisation roles and controlled member invitations
  • Project membership and dataset permissions
  • Encrypted SAV versions outside the relational database
  • Activity history for relevant team actions
  • Optional Microsoft Entra / Office 365 sign-in foundation

Collaboration without real-time editing complexity

The initial collaboration model is deliberately version- and review-based, not Google-Docs-style simultaneous editing. This matches the file-oriented handover process while keeping conflicts, locking and audit behaviour understandable.

For work that belongs on only one device, the separate free Local viewer remains available without a server upload.

Practical workflow
  1. Create a project

    Define the organisational context and add only the people who need access.

  2. Upload explicitly

    Choose the Teams workspace and upload the SAV file over HTTPS into encrypted storage.

  3. Create a named version

    Inspect or edit the working copy, then save a complete version with a concise comment.

  4. Review the exact state

    A colleague opens that version and records an approval or rejection.

FAQ

Frequently asked questions

Are Teams files encrypted?

Yes. Persisted file versions are encrypted with authenticated AES-256-GCM encryption; transport uses HTTPS and access is checked server-side.

Can anyone register for Teams?

No. External self-registration is disabled during the managed pilot phase. Access is provisioned or invited in a controlled organisation context.

Does Teams support simultaneous live editing?

Not currently. The product uses explicit immutable versions and reviews, which fit the controlled SAV handover workflow without hiding conflicts.

Can we keep some files local?

Yes. SAV Inspector Local remains a separate no-upload application for files that do not need shared storage.

SAV Workflow Check

Find out in 30 minutes whether SAV Inspector fits your workflow.

We take one concrete recurring SAV job, define the desired outcome and demonstrate the shortest Local or Teams path. No generic product presentation, no newsletter and no file upload by email.

  • one concrete workflow instead of a feature tour
  • no-upload Local demo or controlled Teams pilot
  • a shared success criterion
  • a clear recommendation — including when SAV Inspector is not a fit

Only used to reply personally to this request. No newsletter. No SAV file or file metadata is transferred through this form. Privacy Email us directly