Skip to content

Licensing and permissions ​

Feature licensing, member roles and resource permissions are separate. A license does not make someone an administrator, and administrators do not automatically read every private result.

Feature licensing ​

Released and development versions are transitioning between authorization systems. Check your installed status and corresponding release notes.

The older system distinguished Basic and Pro. Basic provided core processing and single-sample Origin export. Pro added batch and template exports, presets, workflow and plot templates, formulation tools, experiment databases and dataset export.

The newer direction uses laboratory accounts with authorized, unauthorized and relevant read-only states. Legacy activation instructions do not apply uniformly to every version.

Members and devices ​

After installation, sign in or request laboratory membership through the software. Laboratory rules determine approved members and devices. Availability also depends on version, licensing and server capabilities.

Roles and data permissions ​

ConceptDetermines
Feature licenseUse of a software feature
Member and device eligibilityConnection to laboratory services
Administrative roleAuthorized governance of members, devices and dictionaries
Object permissionsViewing, exporting, changing or publishing a specific resource

Members may save local results and submit eligible data when licenses, sources and object permissions allow. Permission to view or export someone else's data does not necessarily permit republication.

Uploading is not sharing ​

Sample sharing and result permissions are evaluated separately. Current cloud analysis results are creator-private; uploading, linking a readable sample or having an administrator role does not make them available to the whole group.

Internal workflows, Origin templates and scripts are shared with specifically authorized members.

Where to start ​

This legacy help address is retained for existing software links. It does not sell purchases, payments or activation codes.

Built for experiment data workflows.