By role
Permissions defined once
A role carries its module access and its signing rights. People are assigned to the role rather than configured one at a time, so access is consistent across the project.
Access Control
A signature only means something if the signer was allowed to give it.
Deskely controls who sees what, who can execute records, and who can sign them — by role, by company, and for a defined period. Multi-contractor projects stay open enough to work in and tight enough to defend.
No credit card required · 14-day free trial
Per surface
Web and tablet decided separately
Signing checksheets in the field is not the same right as signing them at a desk. Each role states where it can sign, so authority matches how the work is actually done.
Time-bound
Assignments with start and end dates
Contractors, vendors and rotating crews get access for the period they are on the project, and it lapses on its own when that period ends.
The Problem
Everyone gets admin because it was faster at setup.
A commissioning project runs on people from several companies who arrive and leave at different times. Getting them productive quickly usually wins over getting their access right, so permissions are handed out broadly and shared logins appear on the tablets in the field.
The consequences arrive later. A vendor who demobilised months ago still has an active account. Reference data is edited by someone who did not know what depended on it. A checksheet is signed by a name that has no defined authority to sign it, and nobody can say afterwards whether it should have been.
At handover this becomes a documentation problem rather than a security one. The client asks who signed a record and under what authority, and the honest answer is that the system allowed anyone to. Packs get rejected, records get re-signed, and the schedule absorbs the difference.
How it works
Define the job once, then assign people to it.
Access in Deskely is built from roles rather than from individual exceptions, so a new contractor arriving in month nine gets exactly the same access as the one who arrived in month one.
WIRE
Create the role
Define a role for a job on the project — field technician, discipline lead, commissioning manager, vendor specialist — with a name and a description of what it is for.
WIRE
Toggle module access
Switch modules on or off for the role. What is off is not simply greyed out: it does not appear in the menu, so people work in the part of the project that belongs to them.
WIRE
Decide where it can sign
Choose whether the role can sign checksheets in the web app, the tablet app, both, or neither — so signing authority reflects how and where that job is actually done.
WIRE
Set up the companies
Add the contractors, vendors and operators on the project, each with its own assignment period, so people are grouped by the organisation they answer to.
WIRE
Assign people with dates
Invite a user or assign an existing Deskely account to the project with a role, a company, and start and end dates. Access begins and lapses on its own.
CONTINUITY
Authority you can point to
Every signature on the project traces back to a role that was permitted to give it, on a date the signer was assigned.
In Practice
The same record looks different depending on who opens it.
A technician on the tablet sees the work: readings to record, photos to attach, a punch to raise if something fails, and the executor signature that belongs to their job. The acceptance step is simply not offered to them.
The discipline lead opens the same record in the web app and sees who executed it, when, and with what evidence — plus the acceptance signature their role is permitted to give. Nobody is blocked by a message telling them to ask someone else; the interface only presents what the role can actually do.
This is what keeps a large multi-contractor project navigable. People see their own scope rather than the whole platform, the menu is short, and mistakes that come from working in the wrong area of a project stop happening.
Assurance
Who signed, in what role, on which day.
Access control is what makes the rest of the audit trail worth having. These rules hold across every module, on web and on tablet, for every company on the project.
Every user is a named account — signatures carry a person, a role and a company, never a shared site login
Signing rights are set per surface, so a role can be allowed to sign on tablet, on web, on both, or on neither
Modules that a role has no permission for do not appear in that user's navigation at all
Assignments carry start and end dates, so access for contractors and vendors lapses without a manual cleanup task
Sensitive configuration such as master data is a distinct permission rather than a side effect of seniority
Signatures record the role and company in force at the time, so an audit can be answered years later
When a client questions a signature, the record answers for itself: the person, the company they worked for, the role they held, the authority that role carried, and the period they were assigned to the project.
Business Outcomes
What this changes for your project.
New crews productive on day one
Assign someone to an existing role and they have exactly the right access immediately — no per-person configuration and no waiting on an administrator.
People see their own scope
A short, relevant menu means fewer mistakes in the wrong part of the project and far less training for contractors who are only here for one phase.
No orphaned accounts
Assignment dates end access when a company demobilises, so the project does not accumulate active logins nobody is responsible for.
Handover packs that survive review
Every signature in the dossier was given by a role permitted to give it, which is exactly the question an operator's audit team asks first.
FAQ
Frequently asked questions.
Related Modules
Works seamlessly with other modules.
Master Data
Manage tags, systems, subsystems, documents, and personnel that power every module.
Commissioning Procedures
Design, publish, and execute controlled commissioning procedures with structured sign-off flows.
Certificates
Monitor project readiness and track prerequisites based on G-series certificate standards.
