What this role is accountable for
Understand headcount, organization, hiring, goals, time off, compensation, and pending decisions from one governed workspace.
- Know the right context
- Make or prepare decisions
- Hand off to the next owner
For founders and executives
One system, not escalations.
- Headcount, hiring, and goals read from live records.
- Pending decisions surface without an escalation chain.
- Sensitive totals stay scoped to who is allowed to see them.
How it works
Concrete product states, permissions, and handoffs
Each demonstration uses fictional sample data and keeps the source record, actor, permission boundary, and next step visible.
What they see when they open Perelan
A role-specific home surface combines relevant status, records, requests, and assistant prompts without exposing unrelated sensitive detail.
Actions the assistant can take with their access
The assistant can answer, draft, or prepare actions from the same permissions as the user. It is useful because it is bounded, not because it has a separate authority.
Handoffs to other teams
Approvals, access requests, hiring transitions, compensation proposals, and integration setup all keep a source record and next owner visible.
Product map
Follow the next useful path
These links are curated for the page rather than generated at random.
The Perelan platformOne workspace. Shared context. Less operational drag.Connect people, time, growth, money, decisions, and AI in one permission-aware workspace.Security at PerelanSecurity is part of the action path, not a page added after it.Understand how Perelan approaches authentication, authorization, service identity, integration security, AI boundaries, auditability, files, tokens, and incident readiness.ImplementationA new people platform should not become a second full-time migration project.Plan your Perelan rollout with guided discovery, data preparation, workspace configuration, integration setup, validation, training, launch, and follow-through.
Questions
What buyers usually ask
Answers are scoped to repository-verified behavior or intentionally point to current customer documentation when policy facts are not public.
No. The marketing examples are compressed, but the product path still checks the acting user, role, group scope, and domain permission before data is shown or changed.
No. The product demonstrations use fictional names, roles, dates, and values so the workflow is clear without exposing real people or companies.
Yes. Workspace roles, manager scope, and group-lead capabilities define what each person can see and do.
Yes. Implementation can start with core records and self-service, then add lifecycle workflows, integrations, analytics, and AI surfaces.
Next step
Build a people operation your team will actually use.
Start with the workflow you want to make calmer, then map the people, records, permissions, and handoffs that make it real.