Commit 581b7b8b authored by Ernst van Nierop's avatar Ernst van Nierop

Merge branch 'patch-16' into 'master'

small step update on CAN

changed beginning steps on process to update CAN

See merge request !1861
parents 58640f05 77382de5
Pipeline #1514579 passed with stages
......@@ -32,18 +32,16 @@ NOTE: Our contractor agreements and employment contracts are all on the [Contrac
## Regular compensation <a name="regular-compensation"></a>
1. Employees of our Dutch entity (GitLab B.V.) will get their salary wired on the 25th of every month, and can see their payslip in their personal portal on [HR Savvy's system](https://hr-savvy.nmbrs.nl/).
1. Employees of our US entity (GitLab Inc.) have payroll processed semi-monthly through TriNet, and they can access their pay slips through the [TriNet portal](https://www.hrpassport.com).
1. Employees of our Dutch entity (GitLab B.V.) will get their salary wired on the
25th of every month, and can see their payslip in their personal portal on
[HR Savvy's system](https://hr-savvy.nmbrs.nl/).
1. Employees of our US entity (GitLab Inc.) have payroll processed semi-monthly
through TriNet, and they can access their pay slips through the [TriNet portal](https://www.hrpassport.com).
1. Contractors to GitLab (either entity) should send their invoices for services rendered to ap@gitlab.com
* For 'fixed fee' contracts, it is OK to send the invoice before the time period
that it covers is over. For example, an invoice covering the period of March 1-31 can be sent on March 25.
* All invoices are internally reviewed, approved, and then payment is processed.
This is usually a fast process, but be aware that it can incur delays around vacations.
1. Any changes to a Contributor's status, classification, promotion/demotion,
pay increases/decreases, and bonus need to be communicated to People Operations
by the manager or CEO. People Operations then records this formally (for audit purposes)
in a Contributor Action Notice (CAN).
## Specific to employees based in the Netherlands <a name="nl-specific-benefits"></a>
......
......@@ -6,6 +6,7 @@ title: "People Operations"
- [Reaching People Operations](#reach-peopleops)
- [Setting up new contracts](#new-contracts)
- [Using HelloSign](#hellosign)
- [Processing changes](#processing-changes)
- [Using BambooHR](#bamboohr)
- [Adding a new team member to BambooHR](#admin-bamboo)
- [Using BambooHR as a new team member](#new-member-bamboo)
......@@ -27,6 +28,7 @@ member of the People Operations team, as listed on our [Team page](https://about
New team hire contracts are found on the [Contracts](https://about.gitlab.com/handbook/contracts/) page, including instructions on how to set up new contracts.
Templates for the contracts are set up in BambooHR. You can download the template from the "Files" tab and work on the contract using Google Drive. Here you can work together if you need help and download the PDF for HelloSign.
### Using HelloSign<a name="hellosign"></a>
When we need [contracts to be signed](https://about.gitlab.com/handbook/#signing-legal-documents) we use [HelloSign](https://hellosign.com).
......@@ -44,6 +46,19 @@ Follow these steps to send out a signature request.
Once you've sent out the document you will receive email notifications of the progress and a copy of the signed document after all parties have signed.
## Processing changes<a name="processing-changes"></a>
Any changes to a team member’s status, classification, promotion/demotion, pay increase/decrease and
bonus needs to be communicated via email to People Ops by the team member's manager or CEO. People Ops will then enter
the changes in BambooHR under the Jobs Tab in the member’s profile; then file the email in the Offers
and Contracts Folder in the Document Section.
Further changes may need to be [processed in TriNet](#changes-trinet) or Savvy to fully process the change. People Ops
is responsible for seeing the change through to completion. Once completed, People Ops
sends an email to the person reporting / requesting the change (member's manager or CEO)
to confirm this.
## Using BambooHR<a name="bamboohr"></a>
We’re using [BambooHR](https://gitlab.bamboohr.com) to keep all team member information
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment