Begin of the insertion**As** aEnd of the insertion Begin of the deletion As part ofEnd of the deletion resource Begin of the insertionmanager
**I want to** track forEnd of the insertion Begin of the deletion planning, we need to be able to configureEnd of the deletion each user Begin of the insertionin the system on what weekdays they work, how manyEnd of the insertion Begin of the deletion workingEnd of the deletion hours Begin of the insertionper dayEnd of the insertion Begin of the deletion (start time and end time), daily or weekly working number of hours, whetherEnd of the deletion they Begin of the insertionwork, when theyEnd of the insertion are Begin of the insertionnot available
**so that** I can properly plan my resources.

**Acceptance criteria**

* For every user in the system it is possible to track

* Working days

* How many hours per day they work.
We chose this overEnd of the insertion Begin of the deletion on vacation onEnd of the deletion a Begin of the insertionweekly work time so we can properly overlayEnd of the insertion Begin of the deletion certain date. FromEnd of the deletion this Begin of the insertionwith work packages

* An _availability factor_. We acknowledge that users will not always work 100% on project work. Daily business and other stuff happens. SoEnd of the insertion Begin of the deletion infoEnd of the deletion we can Begin of the insertionspecify this factor (i.e. user works 40hrs per week, availability factor of 80% --> 32hrs of resource availability)

* Vacation times and other unavailable days should be trackable. For privacy reasons, no more details than just unavailable days should be tracked (i.e. no differentiation between holidays and sick days)

* There should be a setting, if those hours can be edited by users themselves, only with a certain role, or not at all

* The settings should be changeable byEnd of the insertion Begin of the deletion calculateEnd of the deletion the Begin of the insertionAPI

* Modification should be handled by a new tab in the user edit page.


**Technical notes**

* Availability times should be logged like hourly rates. With a starting date. That will work properly with users switching from full to part time, etc

* OldEnd of the insertion Begin of the deletion user'sEnd of the deletion availability Begin of the insertionrecords cannot be edited but new ones can be added.


**Permissions and visibility considerations**

* Users should see their own times

* If the self-service setting is enabledEnd of the insertion Begin of the deletion soEnd of the deletion that Begin of the insertionusers can do self-editing of times, users can edit their own times

* If the self-service setting is disabled, only users with the `Manage user working hours` permission are allowed to edit times


**Translation considerations**

* _Key terms and phrases in the key languages_ 


**Out of scope**

* We do not want to become an HR system. So things like vacation requests, etc will not be implemented

* The UI to manage the data is a help for smaller customers. We expect the data to mostly be injected into our system by an external service (HR system, etc) via the APIEnd of the insertion Begin of the deletion when assigning tasks it would display available resources only.End of the deletion