Teams often need data from people who should not have full Labsheet access.
So they fall back on workarounds:
That creates extra reconciliation work and makes it harder to keep submissions tied to the right records.
It also adds risk around visibility and process control. External users should not see each other’s data. Host teams still need every submission to land cleanly in the backing Labsheet and stay logged, even when something fails.
This setup lets a locked Labsheet power a form.
Admins choose which columns to expose, assign the form to external orgs or users, and publish it through a portal. External users log in, fill out the form, and each submission creates a row in the backing Labsheet.
The same system also works for internal teams that need a simpler entry surface inside Scispot.
Core rules stay intact:
Each form submission maps 1:1 to a row in the backing Labsheet, with no copy-paste step in between.
External users only see their own submissions, and lookup options are scoped to their org.
Every submission, including failures, keeps a raw log with status, errors, and row links for review.
A super admin locks the schema. Then an admin selects the columns to expose and publishes the form.
How it works.
The form is assigned to external orgs or users. Submitters log into the portal and enter data or upload CSV files.
Each submission creates Labsheet rows, stores a permanent log, and gives host teams one place to review issues and respond.
Pick a locked Labsheet, choose exposed columns, set labels and required fields, and preview before publishing.
External users log in, see assigned forms, submit single entries or CSV batches, and track their own submissions.
Host teams can filter submissions by form, org, status, and date, then click through to the related Labsheet row.
External users can add comments and attachments after submission, while host teams review and resolve exceptions.