Begin of the insertion### User Story

**AsEnd of the insertion Begin of the deletion **As**End of the deletion a Begin of the insertionuser** with permission to log time on behalfEnd of the insertion Begin of the deletion \[enter roleEnd of the deletion of Begin of the insertionothersEnd of the insertion Begin of the deletion user\]End of the deletion
**I want to** Begin of the insertionlog one time entry for multiple users at once in the mobile appEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionI can quickly record shared work without repeating the same form per userEnd of the insertion Begin of the deletion \[enter desired result\]End of the deletion

Begin of the insertion### Acceptance CriteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertionThe time tracking screen provides an entry point (e.g., “+” action) that offers “Log time” as an action.

End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertionWhen “Log time” is opened, the form contains a **Users** field ifEnd of the insertion Begin of the deletion <br>


**PermissionsEnd of the deletion and Begin of the insertiononly if the current user has the permission to log time for other users.

End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertionIf the current user does **not** have the permission to log time for other users:

* The **Users** fieldEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertionhidden.

* The time entry will be logged **only for the current user**.

* If the current user **does** have the permission to log time for other users:

* The **Users** field is visible and allows selecting **multiple users**.

* The current user is preselected by default.

* Tapping the Users field opens a user-picker list with:

* A search input to filter users by name.

* Multi-select checkboxes for users.

* A clear indication of the current user (e.g., “(me)”).

* A confirmation action (e.g., “Select”) that returns to the Log time form.

* The Log time form requires the same mandatory fields as single-user logging.End of the insertion Begin of the deletion this feature visible?_End of the deletion

* Begin of the insertionOn Save with multiple users selected:

* The app creates **N time entries**, one per selected user, with identical field values (work package, date, activity, comment, duration/times).

* The app shows a single success confirmation that indicates how many users were logged (e.g., “Logged time for 3 users”).

* If creation fails for one or more selected users:

* Always an “all-or-nothing” behavior (no entries created if any fail) must be defined and implemented consistently.

* The Users picker must not allow selecting users that the current userEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the deletion itEnd of the deletion not Begin of the insertionallowed to log time for.

End of the insertion Begin of the deletion visible?_


**Translation considerations**

End of the deletion * Begin of the insertionOnly the created time entries for yourself are visibleEnd of the insertion Begin of the deletion _Key terms and phrasesEnd of the deletion in the Begin of the insertionrelevant mobile views.End of the insertion Begin of the deletion key languages_&nbsp;End of the deletion


Begin of the insertion### Technical NotesEnd of the insertion Begin of the deletion **Out of scope**End of the deletion

Begin of the insertion<br>

### Permissions and Visibility Considerations

End of the insertion * Begin of the insertionPermission gate:

* The abilityEnd of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _fieldEnd of the deletion to Begin of the insertionselect and log time for other users requires a dedicated permission (e.g., “Log time for others”).

* UI visibility:

* Without permission, the Users field is hidden and implicitly fixedEnd of the insertion Begin of the deletion include all teams necessaryEnd of the deletion to Begin of the insertionthe current user.

* With permission, the Users field is visible and editable, allowing multi-select.

* Target user visibility:

* The user picker must only expose users that the actor is allowed to see (per workspace/user visibility rules).


### Translation Considerations

* Key UI strings requiring localization:

* “Users”


### OutEnd of the insertion Begin of the deletion be informedEnd of the deletion of Begin of the insertionScope

* Changing or redefiningEnd of the insertion the Begin of the insertionunderlying permission model (only consuming an existing permission is in scope).

* Bulk editing or bulk deleting time entries.

* Aggregated “shared” time entries that remain a single record linked to multiple users (explicitly not covered unless the data model is redesigned).End of the insertion Begin of the deletion changes._End of the deletion