Who can see what: sharing survey data without losing control
In most organisations, survey data is still distributed the way it was delivered: as files. LumiDB answers the question in the archive itself. Access rights are set once, per person and per project, and enforced on every route into the data.
Written by
Published on
Do not index
In most organisations, survey data is still distributed the way it was delivered: as files. A shared folder grants access to everything in it, and a file sent onward cannot be recalled. When the only choices are full access or none, data owners choose none, and the archive stays with the few people entitled to open it.
So access gets granted by delivery instead. The surveyor clips a subset and sends it each time a client or colleague needs a piece of a project. As projects accumulate rasters, vectors and drawings alongside the point cloud, the number of copies in circulation grows faster than anyone’s record of them.
LumiDB answers the question in the archive itself. Access rights are set once, per person and per project, and enforced on every route into the data: the web viewer, a share link, an API key and the streaming connections all check the same rule. A right granted or revoked in one place applies everywhere, whatever the data type or tool.
Each project has its own access list with three levels: full access, download, or view-only. A client or contractor is added as a guest and sees only the projects they are invited to, with whatever level they were given there. View-only is not confined to the browser; every level can measure, inspect and stream the data straight into their own GIS or CAD. What no one gets without the right is a file. The data stays in the archive; the work happens on it.
A project can also be opened deliberately to anyone through a link, with no account required, for a public consultation, a tender package or a stakeholder presentation. The link exposes only that project and can be withdrawn at any time, so making data public is a decision, not an accident.
Invitations go through the identity provider and are revoked together with project access when a person is removed. API keys belong to an individual user and inherit that user’s permissions. For organisations whose data cannot leave their perimeter, the Enterprise tier runs inside their own cloud or on-premises environment.
Customers shaped this model, and several further needs sit on top of it: access that expires with a contractor’s engagement, an audit log of who opened or exported a dataset, approval before an export leaves the archive, or roles mapped to an existing directory group.
If you’d like to see the access model on your own projects,, write to us at sales@lumidb.com or book a call here.
Written by
