How do teams work, and who can see whom?

A team is two things at once: a label on reports and a boundary on what a manager may look at. Every employee belongs to exactly one team, chosen when they are invited.

Creating a team

1. Open the workspace name at the top of the sidebar and choose Employees.
2. Switch to the Teams tab and press Add team.
3. Give it a name and pick one of the eight colors, then save.

Spell the name out in full. Worktivity uses it when suggesting which applications count as productive for that team, which is covered in deciding which apps count as productive.

A team can be deleted only while it is empty, and the confirmation asks for your password. Move the people out first.

The four roles

• Owner: one person, the one who created the organization. Only the owner can delete it or open the subscription screen. The role cannot be handed to anyone from the invite form.
• Co-owner: the same reach across employees, settings and reports, without the two owner-only screens.
• Manager: sees their own team and nothing else.
• Employee: sees their own records and nothing else.

What the manager boundary actually covers

The limit is applied on the server, not by hiding buttons. When a manager asks for the employee list, the timesheet, screenshots, timelapse videos, activity logs, work times, app reviews, leave requests or the advanced insights, the request is rewritten to their own team before it runs.

A team is a visibility boundary. Moving someone into another team changes which manager can look at their records, so treat it as an access change, not a label change.

What managers can do beyond looking

A few extra powers are switches, not part of the role. In Organization settings, on the Tracking tab, the Permissions card decides whether managers may see app reviews and whether they may change them. With those switches off, the screen does not appear in their sidebar at all.

Moving someone

Open Edit employee from the row menu and pick another team. Blocking, removing or moving an employee describes when the change takes hold.

Plans cap how many teams an organization may have, and the form shows how many are left. The count is enforced in the interface; the server does not repeat the check.