Teams & organisation
OpsQI works the way your organisation does.
Departments, teams, people and roles.
The problem
Tools don't know your org chart.
Who reports to whom, who is on leave, who should see what — if the tool doesn't know, alerts go to the wrong person and data is exposed to the wrong people.
AI in this module
Signals get their context from here.
- Department and team working hours feed delay and inactivity calculations
- People on leave and new joiners are excluded from inactivity analysis
- Alerts route through the hierarchy to the team lead, department manager or CTO
What you can do
Nested departments
A tree via parent departments, with a manager and working days/hours.
Teams
Team lead, members, team workload and idle-members views; teams can set their own hours.
Custom roles and permissions
Custom roles beyond the 6 system roles: colour, hierarchy and a permission list.
Invitations
Role, team, department and salary set in advance; valid 72h and resendable.
Role-based onboarding
A step checklist per role, progress percentage and a restartable tour.
Leave and hand-over
Leave dates; when someone leaves, their tasks, reviewer and leadership roles move to a chosen successor and their tokens are revoked.
Who uses it and how
CTO
Defines roles and permissions, sets up the organisation.
Department Manager
Manages teams and working hours.
Team Lead
Sees team workload and idle members.
Frequently asked
Is access tied to the role name?
No. Access comes from the permissions on the workspace membership; custom roles let you fine-tune them.
What happens to someone's work when they leave?
The hand-over flow moves open tasks, reviewer roles, leadership roles, pool items and escalations to the person you choose.
See it with your own data.
Open a free workspace, or let's schedule a demo with your team.