ND
Northstar Digital
Group of companies
40 employeesTeam section
Team members, availability, and pending actions
Employees and managers open the same section with the same tabs: the roster, who is available, the actions that need their own input, and a shared absence timeline. A permission adds actions inside that one shell rather than opening a second interface.
Four tabs, four URLsRoster from the org structureShared absence timelineEnabled by arrangement
app.teamevo.co/main/structure
Search or run a command…⌘K
Control centre
7Kate EllisAdministratorFind a department or a person
Tree Org chart List
With employees only40 employeesPP
Product and platform
Anna Reed
19 employeesSA
Sales and accounts
Max Turner
10 employeesMB
Marketing and brand
Ellen Shaw
5 employeesPC
People and culture
Kate Ellis
6 employeesC
Commerce
Ian Prescott
1 employeesHow the Team section is used
- 1
Open the overview
Counters for team size, who is away today and active reviews, and beneath them the list of actions waiting on you personally, each linking into the screen that resolves it.
- 2
Review the members
The roster carries photo, name, job title, department and an away-today label, loaded a page at a time. The section states 'showing 200 of 1240' rather than passing the first two hundred off as the whole team.
- 3
Open a colleague's card
Who they are and how they connect to the team, whether they are available today, recent public thanks, review status with a way in, the current onboarding step when one is running, and a link to the full profile.
- 4
Plan the absences together
A horizontal timeline over three, six or twelve months with a row for every member, including people with no entries. The question it answers is who will be away when.
- 5
Add your own period
Under the timeline is a form for your own absence: type and dates. Other people's bars are read-only, and the server calculates the right to edit rather than the interface hiding the button.
What the section does
One shared space for everyone in the team
An employee and their manager open the same screen with the same tabs. A permission such as running a review adds an action inside that shell instead of creating a separate manager area.
ADR-002: the manager-cockpit design was reviewed and cancelled
Membership computed from the org structure
A team is the manager's circle — a manager and their direct reports — falling back to the department when the reporting line is empty. Teams are not created by hand.
A team identifier is opaque and re-checked against the asker every time
Four tabs, each its own address
Overview, Members, Reviews and Absences. A tab is a URL rather than internal state, so a link to Reviews can be sent to a colleague and the browser back button works.
/main/team/:tab
Attention without surveillance
The 'needs attention' list holds only what the system is waiting on from you personally, and each item links to the screen that clears it.
Lines of the 'Maria has 5 overdue tasks' shape are forbidden by the architecture decision
Counters that admit when they do not know
If the absence source or the review module is unavailable, that tile is hidden rather than showing a zero. A zero would read as 'nobody is away today', and the portal cannot make that statement at that moment.
The count is optional in the API rather than defaulting to zero
A failed source is named
If recognition, reviews or programs do not answer, the member card does not render them empty: each section is isolated and the failed source is listed separately.
'No thanks yet' and 'we could not ask' look alike and mean different things
A colleague's sick leave is anonymised
Without a specific permission a viewer sees a neutral 'Away' instead of 'Sick leave', and free-text reasons are stripped. The owner of the record always sees their real type.
One rule applied on every read path, not per screen
Reviews open on their own screen
The Reviews tab hands the space to the performance review module and copies none of its data. If a customer has reviews switched off, the other tabs keep working.
The section owns nothing: it assembles what other modules own
Someone outside your team is indistinguishable from someone who does not exist
Requesting a colleague from another team and requesting a non-existent person return the same 'not found'. A different answer would confirm that employee exists to someone with no right to ask.
404 rather than 403, deliberately
An employee with no department still gets in
If neither the reporting line nor the department is filled in, the section does not disappear: Members and Absences remain, and the person sees themselves and plans their own periods.
Hiding the section would take away planning over missing HR data
Team roster in the mobile app
The app carries a team screen: members with photo, job title, department and an away-today label, with a link into the profile.
The overview, reviews and the absence timeline are web-only
Frequently asked questions
No. It was designed as one and that design was cancelled by an architecture decision. The Team section is a shared space for everyone in the team: an employee needs to mark their own absence dates while seeing colleagues, and a manager needs the same shared picture. A permission adds actions inside the same shell.
Related TeamEvo capabilities
People and org structureWhere team membership and manager relationships come from.My tasksThe personal list of actions waiting on you across the portal.Performance reviewThe module the Reviews tab hands the screen to.Employee onboardingThe program whose current step appears on a member's card.TeamEvo for managersWhat a manager's day looks like across the portal.PricingEvery module in one plan, free up to 20 employees.
Ask about enabling the Team section
The section is enabled per customer. We will look at your org structure and access model before switching it on.