Identity and network access
Federate the vendor’s identity provider where needed. Set network permissions for the client systems the engagement uses.
Give contractors a desktop for the project.
Set up a browser desktop with the applications, files and network access each engagement needs. Apply transfer rules and revoke access when the work ends, without shipping a laptop.
Laptops and VPN accounts outlast the work.
A shipped laptop must be enrolled, tracked and returned. A VPN account can reach more of the network than the project needs.
Assign what each contractor can reach.
Assign an approved image and the project’s applications, files and network permissions. The contractor opens the desktop in a supported browser.
A supported browserNothing to install. No device enrollment.
Signs in
Assign accessUsers, applications and network permissions
Reaches
Per engagementOne desktop per contractor
Approved applications
Project files
Data transfersBlock or allow clipboard, downloads and printing
Other projectsSeparate desktops, files and network permissions
Files and recordsFollow the agreed retention rules
- Project template
Approved applications and access for the engagement
- Identity
Your identity provider or the vendor’s federated provider
- Deployment
Neverinstall Cloud, your cloud account or your own servers with Neverinstall Private Cloud
- Pricing
Per user, per month. Infrastructure is quoted separately.
Agree on identity and record ownership.
Retained records
Agree on recording, retention periods and authorized reviewers. Keep those permissions separate from the contractor’s access after the engagement.
Test access removal on the engagement’s last day.
Agree on transfer rules and retained records before the engagement starts.
Prepare the project
Assign the desktop image, applications and network permissions. Set recording and retention rules, including who may review records.
Test the contractor account
Check approved access and blocked attempts to reach another project’s desktops, files and networks. Test clipboard, downloads and printing on the chosen client.
Rehearse closure
Revoke a test account during an open session and confirm when it closes. Check that authorized reviewers can still reach retained project files and recordings.
Related
Questions about contractor access.
What does onboarding involve?
Create a desktop from the project’s approved image, assign access and send the contractor a link. They open it in a supported browser, with no installation or device enrollment.
Can contractors use their company accounts?
Yes. Federate the vendor’s identity provider so contractors can sign in with their company accounts.
How are projects kept separate?
Each contractor has a desktop grouped by client or project, with its own rules and files. Test the desktop and network permissions with contractor accounts before the engagement starts.
Which data transfers can we block?
You can block clipboard, downloads and printing for the engagement. Test each control on the browser or client contractors will use, and confirm when rule changes take effect.
What happens when access ends?
Revoke desktop access and apply the agreed retention policy to files and recordings. In the pilot, test how an open session closes and who can review retained records.
How are short engagements priced?
Neverinstall Virtual Desktops is priced per contracted user, per month, with infrastructure listed separately. Share the expected user counts and engagement lengths so the quote covers that pattern.
Plan access for your next engagement.
Tell us the applications, networks and transfer restrictions each contractor needs. We will review access and offboarding with your team.