Working with Contractors

If there is a need to involve contractors, we define the following simple rules:

Contractors working for VSHN

Contractors which are working directly for VSHN, where the work isn’t directly billed to customers, need to be checked for objections with Finance and People Role.

Examples:

  • A contractor which develops something for VSHN

  • A contractor which supports VSHN when there is a personnel shortage

Contractors working for VSHN customers

When a contractor works for a VSHN customer in VSHN’s name (subcontractor) and the work is directly paid by the customer, then it’s up to the team (domain accountable) to decide.

In general, we try to avoid this and want to do as much ourselves to preserve knowledge and keep the money at VSHN.

How-To enable access to VSHN

To enable an external contractor to access VSHN systems, the following prerequisits have to be in-place:

  1. Create a Jira issue in the VCI project to leave a trace about this

  2. Signed NDA stored in the wiki

  3. Signed contract stored in Nextcloud

VSHN resources an external contractor could have access to:

Confluence

See tutorial in the wiki

VSHN Chat

Add the person in control.vshn.net with service access RocketChat VSHN.

GitLab

TODO

This domain is tracked and reviewed as VIP-161