Context, not copy-and-paste
The assistant works with product tools and page context so the user does not need to paste private records into a separate system.
AI assistant - Available
Answers that respect access.
- It only reads what you could already open yourself.
- Draft a review or request; you decide when to submit.
- Draft self-reviews stay private until you send them.
Illustrative product view. Sample data is fictional and permission labels are educational.
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.
From an answer to a useful next step
Supported actions include time-off requests, goals, access requests, self-review drafts/submission, peer feedback requests, documents where visible, and generated Views.
Draft first. Submit deliberately.
Draft-sensitive work stays private until the eligible user submits or publishes it deliberately.
History is yours to manage
The assistant works with product tools and page context so the user does not need to paste private records into a separate system.
Permission checks are not a prompt
Supported actions include time-off requests, goals, access requests, self-review drafts/submission, peer feedback requests, documents where visible, and generated Views.
Product map
Follow the next useful path
These links are curated for the page rather than generated at random.
AI-built dashboards - BetaDescribe the view. Keep the data rules.Describe the dashboard you need, generate it from permission-scoped data, and save or share it with eligible teammates.Personal AI automations - BetaAutomate the repeatable work. Keep the boundary visible.Create permission-aware AI automations with triggers, conditions, tools, validation, and clear run history.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.Extensibility - MCPBring Perelan context to the AI client you already use without creating a second permission model.Use revocable, expiring personal tokens to connect supported MCP clients to Perelan tools under the owner's current access.
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.
Do not rely on public marketing copy for vendor-retention terms. Contact Perelan for current data-handling documentation for your deployment.
Only when the current user could read that content in the product. Draft self-reviews remain private until the author submits them.
Consequential submit or publish states are described as explicit user actions. The assistant can help draft and prepare work, but the product still enforces the required action path.
The app includes chat history controls, including deletion and history preferences for the user.
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.
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.