Skip to main content
Home page

Your guide to the central control panel in TeamOhana

Alayna Kolb avatar
Written by Alayna Kolb
Updated over a year ago

Overview

When you log into TeamOhana, the first page you land on is your home page: the central control panel for all of the action items and responsibilities you have in the system.

From the home page, you'll be able to easily access your tasks, comments, mentions, requests and approvals, ensuring your workflows are streamlined and improving your overall efficiency in TeamOhana. The home page also serves as a single entry point for creating new headcount and backfill requests, internal transfers, and terminations.

Benefits of the home page to each persona

The home page of TeamOhana is designed to cater to the diverse needs of every user who logs into the system. It is tailored to align with the specific goals and responsibilities of each user, taking into account their roles and access permissions within TeamOhana.

  • Approvers: The home page provides features that empower approvers to efficiently manage and clear their pending approvals, ensuring a streamlined workflow and prompt decision-making.

  • Talent Teams: Talent teams can leverage the home page to stay updated on the health of the hiring pipeline. This enables them to make well-informed decisions, take necessary actions, and ensure an effective talent acquisition process.

  • Hiring Managers: The home page enables hiring managers to create new requests, collaborate with relevant stakeholders, and obtain necessary approvals. This simplifies the request creation process and facilitates smoother communication within the hiring process

  • Finance: Finance teams can utilize the home page to access critical tasks, like approving headcount and employee change requests, and initiate key workflows that may impact the accuracy of their overall cost and budget reconciliation. This ensures proactive financial management and helps maintain precise financial records.

The following section covers the anatomy of the home page and how to navigate each component.

Create

The top right corner of the home page has an orange "Create" button, from which you can create net new headcount requests, backfill requests, internal transfers, terminations, and scenarios.

No matter which option you click from the Create button, a drawer will open on the right side of the page, prompting you to fill in the relevant details to submit the request, the backfill, the internal transfer, or the termination.

Note that this Create button replaces the "+ Request headcount" button that existed in the former Requests module. It also introduces the ability to create a backfill, internal transfer, or termination from a new page, whereas previously that was possible only from the org chart and headcount ledger.

My Tasks: Headcount

My Tasks shows headcount where some action is required.

You can filter the headcount by their various states:

  • Past due headcount shows you the headcount (that you have access to) that have a target start date in the past. Past due headcount are visible to any persona that has permission to view headcount.

  • At risk headcount shows you the headcount (that you have access to) that have a target start date within 15 days. At risk headcount are visible to any persona that has permission to view headcount.

  • Upcoming headcount shows you the headcount (that you have access to) that are "not started" or "ready to hire" with a target start date within 45 days. This tab will only show for users with either the 'mark as ready to hire' permission and/or the 'link job' permission.

  • Recruiter unassigned headcount shows the upcoming headcount that do not have a recruiter assigned to them.

Depending on user permissions, various actions can be taken for each of the sub-tabs of My Tasks in the widget:

  • From Past due and At risk: users can update the target start date of each headcount

  • From Upcoming: users with the permission to mark a 'not started' headcount as 'ready to hire' can do so. If the headcount is already marked as 'ready to hire,' users with the permission to link the headcount with a job from the ATS can do so from here.

  • Recruiter unassigned: users with the permission to assign recruiters can do so from here.

If you click on any of the headcount under "My Tasks," they will open in a drawer containing additional details about the role.

Clicking the ‘expand’ arrows in the top right corner of the My Tasks widget will take you to one of two places, depending on your permissions. If you have permission to view the Hiring Tracker and you click “expand” from Past due, At risk or Upcoming, you will be redirected to the Hiring Tracker with the same filter applied.

If you do not have Hiring Tracker access but you do have access to the Recruiting Workboard, you will land on the Recruiting Workboard from the “expand” button with those filters applied instead.

Only users with access to the Recruiting Workboard will navigate there after clicking the “expand” arrows from the Recruiter Unassigned tab of My Tasks. If a user does not have access to the Recruiting Workboard but does have the “assign a recruiter” permission, they can do so from the My Tasks widget.

My Tasks: Employees

My Tasks also shows where action is required on employee changes, depending on user permissions.

  • Pending reconciliation shows all pending internal transfers and terminations that have been initiated in TeamOhana.

  • Terminations without backfills shows terminations for which a backfill has not yet been created. These terminations populate from both the HRIS and from the terminations workflow in TeamOhana.

Depending on user permissions, various actions can be taken for each of the sub-tab:

  • From Pending reconciliation: users can reconcile the internal transfers once the HRIS has been updated. Terminations should auto-reconcile, but if they do not, the user has the option to manually reconcile them from here.

  • From Terminations without backfills: users can create backfill requests for the terminated employees.

Clicking the ‘expand’ arrows in the top right corner of the My Tasks widget will take the user to the headcount ledger if they have permission to access it.

Approvals

The Approvals widget shows headcount and employee changes currently in approval, with details like the type of request (new hire, backfill, change request, internal transfer, termination), the job details, and the status. This widget will only appear on the homepage of Admins and users who are part of an approval chain.

Admins will be able to see all in-approval headcount, while other approvers will only see headcount in Approvals when it's their turn to review the request. Requests will be sorted by number of days pending approval, with those that have been pending the longest appearing at the top of the list. Once the request has been in approval for more than 30 days, the 'in approval' status indicator will turn red.

Approvers can click into any of the requests in the approval widget to open the headcount details drawer. Additionally, they can click the arrows in the top right corner to expand the Approvals widget to full screen. This action is useful if approvers want to approve requests in bulk.

Note that the Approvals widget completely replaces the Approvals module that previously existed on the main navigation bar.

Requests

The Requests widget also shows draft headcount, change requests, headcount requests, and employee change requests currently in approval, though it differs from Approvals in that the requests here will be visible to all users with attributes and permissions that give them visibility into those requests.

For example, this means that approvers can see requests before or after its their turn to approve them. It also means that department heads will see requests that have been submitted by their hiring managers. Users will also be able to see their own draft requests here. By default requests are sorted by recency, with newest requests showing at the top of the list.

Users can click into any of the headcount under "Requests" to open additional details about the request in a drawer.

Note that for internal transfers, the changes to the employee's information are bolded. For example, Elise Russell in the screenshot below is staying in the Customer Success division, and remaining an IC-7, but she is moving into the CS-General department and getting a new title.

Just like Approvals, users can click into any of the requests in the Requests widget to be taken to the headcount details page. Additionally, they can click the arrows in the top right corner to expand the Requests widget to full screen.

Note that the Requests component of the home page completely replaces the Requests module that previously existed on the main navigation bar.

Comments and Mentions

The Comments and Mentions component of the home page is available to all users and is separated into three sections: All, Mentions, and My comments.

  • All contains all of the comments on the headcount and employee changes visible to the user (dependent on their permissions and attributes.)

  • Mentions contains all of the comments that other users have left on headcount and employee changes visible to the user where the @mention the user's name.

  • My comments contains all of the comments that the user has added on headcount and employee changes

With Comments and Mentions collected on the home page in this way, there are a number of new features and functionalities available to users:

  • Reactions: users can react with emojis to other users' comments in their feed

  • Editing comments: users can edit their own comments. When they do this, there will be an "(edited)" note in their comment.

  • Deleting comments: users can also delete their own comments.

After 90 days, comments and mentions will no longer be captured on the home page, though the comments will still exist on their respective headcount.

The TeamOhana home page enhances the user experience, streamlines workflows, ensures accurate data, and improves overall system efficiency for all users.

Did this answer your question?