What is a Cohort? A Cohort in Rhumbix is essentially a curated collection of employees. This feature is designed to enhance your experience by simplifying User permissions and improving operational efficiency.
Benefits of Cohorts: The primary benefit of Cohorts is the refined control it offers over permissions. Specifically, it defines who can access timekeeping information about certain employees, allowing for a more organized and secure handling of sensitive data.
Essential Aspects of the Cohorts Feature:
Access Defined by Cohort: While being a part of a Group allows Users to engage with various Projects, their access to timekeeping data is exclusively determined by their Cohort assignment. Each Cohort member can access only the timekeeping information associated with their assigned Cohort.
·Mandatory Assignment: It's crucial to note that every User Role in the Group must be assigned to a Cohort to access any timekeeping data. This is a mandatory step for effective use of the Cohorts feature.
This structure ensures that timekeeping data is precisely and securely managed, reinforcing both operational efficiency and data privacy within your organization.
Cohorts on Mobile! Users can quickly add Cohorts of Team Members to a time card in the Mobile Timekeeping workflow. This is a huge time-saver versus individually selecting all relevant Team Members.
Ready to implement Cohorts in your account?
Follow the steps outlined in this Support Article Setting Up and Implementing Cohorts
Example: Cohorts Feature in Action:
Let's consider Project Manager Chris Austin, who is part of the Service Group. His role requires him to review and manage time entries made by specific Foreman, but not by all Foreman in his Service Group. To facilitate this, we create a Cohort comprising two Foremen: Ace Daniels and Andrew Efron.
Here's how the Cohorts feature works in this scenario:
1. Time Entry Visibility and Approval: Whenever any of these two Foremen (members of Chris’s Cohort) create a Time Card, Chris is able to see and approve the time, but this is conditional on one factor: the Project associated with the Time Card must also belong to the Service Group, Chris's assigned Group.
2. Handling Time Cards Outside the Group: If, for instance, one of the two Foremen creates a Time Card for a Project that falls under a different Group (not the Service Group), Chris will still be able to view the timekeeping data. However, in this case, he won't have the authority to approve or make changes to these time entries because the Project does not belong to the Service Group, Chris's assigned Group.
This tailored visibility ensures that Chris Austin can efficiently manage his team's time entries without the clutter of unrelated data, while also maintaining compliance with organizational procedures.