Invite, grant access and import data

The private native-backend Workspace pilot now includes invitation email, provider-managed registration, explicit project access, reviewed imports and an experimental automation API. These are qualified increments, not a production service certification.

Invite and grant access

Organization owners use Members → Create invitation. The recipient opens the email and signs in with the invited verified address, or chooses Create an account and accept invitation if the configured provider supports registration. If email verification outlasts the sign-in session, reopen the invitation.

Email status distinguishes queued, submitted, failed and cancelled. Submitted means the SMTP server accepted the message; check the recipient inbox/spam folder. Resend after one minute creates a replacement link. Revocation prevents admission, even when an already-sent message arrives later. Links expire after two days.

Organization membership does not grant project access. A project administrator uses Project access to assign viewer/member permissions and optional compute or administration capabilities. Direct grants can be revoked. Team grants require team administration. Owners can preview remaining access before removing an organization membership; the preview cannot inspect projects they cannot administer.

Archive hides a project from the default list. Restore shows it again. Neither changes data access or deletes scientific records. Deletion, transfer and complete organization-wide offboarding are not claimed by these controls.

Review an import

1. Open a project where you have editing permission, then Import data.
2. Select a GeoTIFF surface or a LAS 2.0 curve and enter its explicit mapping.
3. Choose Validate and review. Check sample count, nulls, range, units, scientific meaning and original SHA-256. Nothing has been published yet.
4. Confirm permission to retain the data and choose Publish reviewed asset. Alternatively, cancel before publication.

Imports are bounded to 1.5 MB and 100,000 values. GeoTIFF accepts one Float32/64 band with a declared horizontal CRS. It does not infer a vertical datum. LAS imports one chosen channel, requires the declared channel unit to match, and normalizes M/FT measured depths to metres. Enter a stable well identity and an explicit depth reference, including uncertainty. LAS depth does not imply a horizontal CRS. Missing values remain missing. Unsupported or ambiguous mappings are rejected.

The original bytes remain associated with the imported revision. Exact revisions and derived lineage remain distinct. After an ambiguous network failure, retry the same file and mapping; the publication command is reused. A derived revision may not have its own original uploaded file—open the imported revision for that export.

Connections and developer tools

Connections records intended QGIS consumers and ResInsight publishers of scalar maps. An inventory entry does not start an application. Host status remains unreported until actual host reporting is implemented. Configure credentials on the connector host; follow/pin and reconnect remain application controls. Removing an entry does not stop a producer or revoke its access.

The asset inspector exports credential-free QGIS configuration. Its gateway accepts HTTPS with certificate validation or explicit loopback HTTP through SSH. QGIS still uses its native pilot credential path, not the temporary automation token.

Developer issues a project-scoped credential for the experimental API/CLI. It expires within five minutes and requires its parent session to remain valid. See automation API. Unattended service accounts, OIDC device login and automation project provisioning remain outstanding.

Where OSDU enters

OSDU would serve as the selected scientific backend for import, search, exact reads, publication and change recovery. It can enter before a desktop client connects. It does not replace Workspace screens, the identity provider or application-specific connectors. These workflows currently qualify the native project service. OSDU requires separate type/permission/revision qualification; no silent dual authority or OSDU platform fork is introduced.