Features of The People Ops Manager

The overview shows everyone joining and leaving on one timeline. It counts upcoming starters, lists the onboardings that need attention and highlights overdue work. Readiness is the share of verified tasks, so you see why a person is at risk.

Stores or shows

Counts and lists calculated from cases and tasks: upcoming starters and leavers, ready, at risk and blocked cases, overdue tasks, pending approvals.

Example

A starter begins on Monday with 6 of 10 tasks verified. The laptop task is blocked, so the case is listed as at risk with IT named as the owner.

A case follows one person from signed offer to day one, or from notice to the last day. You create it in the app, from an upcoming starter imported from BambooHR or Personio, or through an AI agent. The task plan is generated when the case is created.

Stores or shows

Name, role, department, location, work mode, manager, HR contact, start date or last day, access level, the systems the person needs and an optional internal employee reference. No compensation, identity documents or health data.

Example

You add a designer starting on 3 March in Berlin. The case gets a task for the contract, the laptop, account access and the manager checklist, each with a due date counted back from 3 March.

Three versioned workflows are included: Standard onboarding, Engineering onboarding and Standard offboarding. Each stage has an owning team, a deadline relative to the start date or last day, and prerequisites. A hard prerequisite locks downstream work until it is done.

Stores or shows

Stages, owner teams, service-level target, approval requirements and the dependency graph, drawn as a diagram you can inspect stage by stage.

Example

In Standard onboarding, Access Approval cannot start before IT Provisioning is done, so the diagram shows it as locked until the identity exists.

The task board lists operational work across HR, IT, Finance and hiring managers. You filter by department, owner, status and escalation, and a handoff map shows where one team waits on another. Task status changes are recorded with who made them.

Stores or shows

Task title, owning team, owner, due date, status, prerequisites, escalation state, linked system and a note with the completion evidence.

Example

Finance has not confirmed payroll set-up three days before a start date. The task shows as overdue and the handoff map shows that the manager checklist waits on it.

Consequential changes become approval requests instead of direct actions, whether a person, a workflow or an AI agent asked for them. Only an owner or admin decides. High-risk requests need an extra confirmation, and a decision cannot be changed afterwards.

Stores or shows

The requested action, its detail and exact payload, who asked and through which channel, the risk level, the decision with an optional reason, and the execution result for Jira and Slack actions.

Example

An agent proposes a Jira ticket "Order replacement laptop" for a starter. It waits as a low-risk request until an admin approves it, and only then can it be executed.

You connect BambooHR, Personio, Jira Cloud, Slack and Microsoft Entra ID with API keys from your own accounts. Keys are tested when you save them and stored on the server only. The app shows the status and the last four characters.

Stores or shows

BambooHR and Personio: upcoming starters, read-only. Jira Cloud: tickets created after approval and their status. Slack: reminders posted after approval to one channel. Entra ID: a read-only check whether a directory account exists.

Example

You connect Personio, open the list of upcoming starters and import two of them as onboarding cases. Nothing is written back to Personio.

Claude, ChatGPT, Cursor and other MCP clients can connect to a workspace with a personal token. The server offers 11 tools to read readiness, preview and create cases, and propose Jira tickets or Slack reminders. Setup steps are on the MCP page.

Stores or shows

Only a SHA-256 hash of each token, a short prefix and the last use time. Read tools return role-filtered fields. Agent actions appear in the activity log.

Example

You ask your assistant which starters in the next 14 days are at risk. It calls the readiness tools and answers with names, blockers and owners that your role may see.

Every member is an owner, admin, operator or viewer. The database enforces these roles, not only the interface. A case can be marked restricted, which hides personal fields from roles without People Ops access.

Stores or shows

Role per member and workspace. A visibility table in Settings shows which team sees which field.

Example

IT sees the name, start date and location of a starter to prepare a laptop, but not the contract status.

The activity log is an append-only record of what people, AI agents and connected systems did. Each entry names the actor, the kind of actor and the object, with a timestamp.

Stores or shows

Actor, actor kind (person, agent or system), verb, object, related employee, related system and time.

Example

Agent "Claude" proposed an access request on Tuesday at 10:12. An admin approved it at 10:40. Both lines appear in the log.

Each workspace has its own subscription, paid through Stripe. Owners and admins choose a plan, see the renewal date in Settings and open the Stripe billing portal to update the card, download invoices or cancel. Plans are described on the pricing page.

Stores or shows

Plan, subscription status, end of the current period and the Stripe customer reference. Card details stay with Stripe.

Example

A Team workspace with 100 people cannot add the 101st person until it moves to Growth in the billing portal.