en:cobi.time:manual:administrator
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:cobi.time:manual:administrator [2026/07/10 11:22] – thuth | en:cobi.time:manual:administrator [2026/07/15 13:06] (current) – thuth | ||
|---|---|---|---|
| Line 20: | Line 20: | ||
| * User Groups | * User Groups | ||
| * User Rights | * User Rights | ||
| + | * System Settings | ||
| + | * Audit Logs | ||
| + | * Teams / Team Hierarchies | ||
| ---- | ---- | ||
| Line 310: | Line 313: | ||
| {{: | {{: | ||
| - | The following explanations according to the subdivisions 1 to 4 in the view above. | + | The following explanations according to the subdivisions 1 to 5 in the view above. |
| 1. The SAP user code is used as the username when logging in. | 1. The SAP user code is used as the username when logging in. | ||
| Line 456: | Line 459: | ||
| **Team Source Mode** \\ | **Team Source Mode** \\ | ||
| Defines which data source is used for team-related information within COBI.time. | Defines which data source is used for team-related information within COBI.time. | ||
| - | Depending on the system configuration, different providers may be available. | + | Depending on the system configuration |
| **Show Cost Center** \\ | **Show Cost Center** \\ | ||
| Line 616: | Line 619: | ||
| This function re-evaluates all existing time bookings, absences, time models, and account balances based on the current configuration and calculation rules. | This function re-evaluates all existing time bookings, absences, time models, and account balances based on the current configuration and calculation rules. | ||
| - | |||
| - | A recalculation may be required after: | ||
| - | |||
| - | * Changes to daily or weekly time models | ||
| - | * Adjustments to absence types or booking data | ||
| - | * Corrections of historical time bookings | ||
| - | * Changes affecting working time calculations | ||
| **Start Recalculation** \\ | **Start Recalculation** \\ | ||
| Line 630: | Line 626: | ||
| **Warning** \\ | **Warning** \\ | ||
| - | This action starts a full recalculation of all time accounts in the system. | + | This action starts a full recalculation of all time accounts |
| The recalculation process can be resource-intensive and may temporarily affect system performance. \\ | The recalculation process can be resource-intensive and may temporarily affect system performance. \\ | ||
| Therefore, it is recommended to execute this function outside of peak operating hours whenever possible. | Therefore, it is recommended to execute this function outside of peak operating hours whenever possible. | ||
| + | |||
| + | ===== Audit Logs ===== | ||
| + | |||
| + | The **Audit Logs** module enables administrators to track and review all relevant changes and activities within COBI.time. | ||
| + | |||
| + | Every logged action is stored with a timestamp, user information, | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ==== Filter Options ==== | ||
| + | |||
| + | The filter area can be used to narrow down the displayed audit entries. | ||
| + | |||
| + | **User** \\ | ||
| + | Filters entries by the user who performed the action. | ||
| + | |||
| + | **Target User** \\ | ||
| + | Filters entries by the user whose data was affected by the action. | ||
| + | |||
| + | For example, an administrator may edit time bookings or master data belonging to another employee. In this case, the administrator is stored as the **User** and the employee as the **Target User**. | ||
| + | |||
| + | **Object** \\ | ||
| + | Filters entries by the affected object type. | ||
| + | |||
| + | Examples: | ||
| + | |||
| + | * Time Booking | ||
| + | * Time Account | ||
| + | * Absence | ||
| + | * User | ||
| + | * Project | ||
| + | |||
| + | **Action** \\ | ||
| + | Filters entries by the performed action. | ||
| + | |||
| + | Examples: | ||
| + | |||
| + | * Created | ||
| + | * Modified | ||
| + | * Deleted | ||
| + | * Recalculated | ||
| + | |||
| + | **Source** \\ | ||
| + | Filters entries by the origin of the action. | ||
| + | |||
| + | Available sources: | ||
| + | |||
| + | * Web | ||
| + | * Mobile | ||
| + | |||
| + | **IP Address** \\ | ||
| + | Allows searching for actions performed from a specific IP address. | ||
| + | |||
| + | **From / To** \\ | ||
| + | The date filters can be used to limit the displayed audit logs to a specific period. | ||
| + | |||
| + | **Reset Filters** \\ | ||
| + | Clears all active filters and displays all available audit log entries again. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Audit Log Overview ==== | ||
| + | |||
| + | Each audit log entry contains detailed information about a specific action. | ||
| + | |||
| + | **Created On** \\ | ||
| + | Displays the date and time when the action was performed. | ||
| + | |||
| + | **User** \\ | ||
| + | Displays the user who performed the action. | ||
| + | |||
| + | **Target User** \\ | ||
| + | Displays the user whose data was affected by the action. | ||
| + | |||
| + | **Action** \\ | ||
| + | Describes the action that was performed. | ||
| + | |||
| + | Examples: | ||
| + | |||
| + | * Working time model created | ||
| + | * Time booking modified | ||
| + | * Time accounts recalculated | ||
| + | |||
| + | **Object** \\ | ||
| + | Displays the affected object type. | ||
| + | |||
| + | **Source** \\ | ||
| + | Indicates whether the action was performed through the web application or a mobile application. | ||
| + | |||
| + | **IP Address** \\ | ||
| + | Stores the IP address from which the action was executed. | ||
| + | |||
| + | **Message** \\ | ||
| + | Contains a short description of the logged action. | ||
| + | |||
| + | **Details** \\ | ||
| + | The **Details** button provides additional information about the selected audit log entry. | ||
| + | |||
| + | Depending on the action, additional information may be available, such as: | ||
| + | |||
| + | * Previous and new values | ||
| + | * Modified fields | ||
| + | * Affected objects | ||
| + | * Date and time of the change | ||
| + | * Executing user | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Export Audit Logs ==== | ||
| + | |||
| + | The **Export** button allows administrators to export the currently filtered audit log entries. | ||
| + | |||
| + | All displayed records, including their associated details, can be exported for further analysis, reporting, or documentation purposes. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Use Cases ==== | ||
| + | |||
| + | Audit Logs can be used for various purposes, including: | ||
| + | |||
| + | * Tracking changes to time bookings | ||
| + | * Reviewing modifications to working time models | ||
| + | * Analyzing time account recalculations | ||
| + | * Monitoring administrative activities | ||
| + | * Supporting internal audits and compliance requirements | ||
| + | * Troubleshooting and root-cause analysis of unexpected changes | ||
| + | |||
| + | The Audit Logs module therefore provides a complete history of all relevant activities performed within COBI.time. | ||
| + | |||
| + | ===== Teams ===== | ||
| + | |||
| + | The Teams module allows administrators to create and manage teams within COBI.time. | ||
| + | |||
| + | Teams can be used to group employees according to the organizational structure of the company. \\ | ||
| + | This helps simplify administration, | ||
| + | |||
| + | {{: | ||
| + | {{: | ||
| + | |||
| + | ==== Creating Teams ==== | ||
| + | |||
| + | New teams can be created using the Create Team button. | ||
| + | |||
| + | The following fields are available: | ||
| + | |||
| + | **Team Name** \\ | ||
| + | Enter a unique name for the team. | ||
| + | |||
| + | Examples: | ||
| + | |||
| + | * Sales | ||
| + | * Production | ||
| + | * Warehouse | ||
| + | * Administration | ||
| + | |||
| + | **Description** \\ | ||
| + | Optionally, a description can be entered to provide additional information about the purpose or responsibilities of the team. | ||
| + | |||
| + | **Parent Team** \\ | ||
| + | This field can be used to create team hierarchies. | ||
| + | |||
| + | If a parent team is selected, the newly created team will become a sub-team of the selected parent team. | ||
| + | |||
| + | Example: | ||
| + | |||
| + | * Company | ||
| + | * Sales | ||
| + | * Production | ||
| + | * Warehouse | ||
| + | |||
| + | This allows even complex organizational structures to be represented clearly within COBI.time. | ||
| + | |||
| + | **Save** \\ | ||
| + | Saves the newly created team. | ||
| + | |||
| + | **Cancel** \\ | ||
| + | Discards all entered information and closes the creation dialog. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Teams Overview ==== | ||
| + | |||
| + | The Teams Overview section is located on the left side of the screen. | ||
| + | |||
| + | All existing teams are displayed here. | ||
| + | |||
| + | **Search** \\ | ||
| + | The search field can be used to quickly find existing teams. | ||
| + | |||
| + | The list is automatically filtered while typing. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Assigning Employees to Teams ==== | ||
| + | |||
| + | After selecting a team, employees can be assigned to that team. | ||
| + | |||
| + | This allows employees to be grouped into departments, | ||
| + | |||
| + | Team assignments can be used for purposes such as: | ||
| + | |||
| + | * Organizing the company structure | ||
| + | * Filtering reports and evaluations | ||
| + | * Managing team leaders and employees | ||
| + | * Providing a better overview of departments and business areas | ||
| + | |||
| + | Changes to team assignments are immediately available throughout COBI.time and can be used in all relevant modules and reports. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Team Source Mode ==== | ||
| + | |||
| + | The currently active Team Source Mode is displayed in the top-right corner. | ||
| + | |||
| + | Depending on the system configuration, | ||
| + | |||
| + | Examples: | ||
| + | |||
| + | * COBI.time | ||
| + | * SAP Business One | ||
| + | |||
| + | If COBI.time is selected as the team source, teams can be created and managed directly within this module. | ||
| + | |||
| + | ===== Team Hierarchies ===== | ||
| + | |||
| + | The Team Hierarchies module provides a visual representation of the organizational structure of all teams maintained within COBI.time. | ||
| + | |||
| + | It allows administrators to view, manage, and analyze relationships between parent teams and sub-teams. \\ | ||
| + | This helps create a clear organizational structure and simplifies the management of departments, | ||
| + | |||
| + | {{: | ||
| + | {{: | ||
| + | |||
| + | ==== Tree View ==== | ||
| + | |||
| + | The Tree View section on the left side displays all teams in a hierarchical structure. | ||
| + | |||
| + | Parent teams can be expanded or collapsed to display or hide their sub-teams. | ||
| + | |||
| + | This provides a quick overview of the overall organizational structure. | ||
| + | |||
| + | **Search** \\ | ||
| + | The search field can be used to quickly locate a specific team within the hierarchy. | ||
| + | |||
| + | Matching teams are automatically highlighted while typing. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Hierarchy Inspector ==== | ||
| + | |||
| + | The Hierarchy Inspector displays detailed information about the currently selected team. | ||
| + | |||
| + | **Team Name** \\ | ||
| + | Displays the name of the selected team. | ||
| + | |||
| + | **Team Path** \\ | ||
| + | Shows the complete hierarchy path of the selected team. | ||
| + | |||
| + | Example: | ||
| + | |||
| + | * Production / Sales | ||
| + | |||
| + | This allows administrators to quickly identify the location of a team within the organizational structure. | ||
| + | |||
| + | **Parent Team** \\ | ||
| + | Displays the parent team assigned to the selected team. | ||
| + | |||
| + | If no parent team is assigned, the selected team is considered a top-level team. | ||
| + | |||
| + | **Sub-Teams** \\ | ||
| + | Displays the number of directly assigned child teams. | ||
| + | |||
| + | **Members** \\ | ||
| + | Displays the number of employees currently assigned to the selected team. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Direct Sub-Teams ==== | ||
| + | |||
| + | The Direct Sub-Teams section displays all teams directly assigned beneath the selected team. | ||
| + | |||
| + | If no child teams exist, COBI.time will display a corresponding information message. | ||
| + | |||
| + | This overview helps administrators quickly identify reporting structures and organizational relationships. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Hierarchy Overview ==== | ||
| + | |||
| + | The **Hierarchy Overview** section provides an alternative view of the selected team and its position within the organisation. | ||
| + | |||
| + | For each team, the following information is displayed: | ||
| + | |||
| + | * Team name | ||
| + | * Hierarchy path | ||
| + | * Number of assigned employees | ||
| + | |||
| + | This overview makes it easier to understand the structure of larger organizations with multiple levels of teams. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Team Management Source ==== | ||
| + | |||
| + | The currently active Team Management Source is displayed in the upper-right corner. | ||
| + | |||
| + | Depending on the system configuration, | ||
| + | |||
| + | Examples: | ||
| + | |||
| + | * COBI.time | ||
| + | * SAP Business One | ||
| + | |||
| + | If COBI.time is configured as the team management source, team hierarchies can be maintained directly within the Teams module. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Use Cases ==== | ||
| + | |||
| + | Team hierarchies can be used for various organizational purposes, including: | ||
| + | |||
| + | * Structuring departments and business units | ||
| + | * Defining reporting structures | ||
| + | * Managing team leaders and employees | ||
| + | * Improving organizational transparency | ||
| + | * Supporting team-based reporting and evaluations | ||
| + | * Creating multi-level organizational structures | ||
| + | |||
| + | The Team Hierarchies module provides administrators with a centralized overview of the entire organizational structure maintained within COBI.time. | ||
en/cobi.time/manual/administrator.1783675331.txt.gz · Last modified: by thuth