Time off - Available
Illustrative product view. Sample data is fictional and permission labels are educational.
How it works
Each demonstration uses fictional sample data and keeps the source record, actor, permission boundary, and next step visible.
This section explains the concrete operating path in Perelan: the actor, the record, the state change, and the permission boundary stay visible instead of becoming a loose note in chat. Request with the right context is described through a fictional but product-grounded state so buyers can understand what changes in the workflow and where the limits are.
This section explains the concrete operating path in Perelan: the actor, the record, the state change, and the permission boundary stay visible instead of becoming a loose note in chat. Decide from one focused card is described through a fictional but product-grounded state so buyers can understand what changes in the workflow and where the limits are.
This section explains the concrete operating path in Perelan: the actor, the record, the state change, and the permission boundary stay visible instead of becoming a loose note in chat. One calendar, several useful views is described through a fictional but product-grounded state so buyers can understand what changes in the workflow and where the limits are.
This section explains the concrete operating path in Perelan: the actor, the record, the state change, and the permission boundary stay visible instead of becoming a loose note in chat. Balances that follow policy is described through a fictional but product-grounded state so buyers can understand what changes in the workflow and where the limits are.
This section explains the concrete operating path in Perelan: the actor, the record, the state change, and the permission boundary stay visible instead of becoming a loose note in chat. Cover is part of the request is described through a fictional but product-grounded state so buyers can understand what changes in the workflow and where the limits are.
This section explains the concrete operating path in Perelan: the actor, the record, the state change, and the permission boundary stay visible instead of becoming a loose note in chat. Approvals can meet managers in Slack is described through a fictional but product-grounded state so buyers can understand what changes in the workflow and where the limits are.
This section explains the concrete operating path in Perelan: the actor, the record, the state change, and the permission boundary stay visible instead of becoming a loose note in chat. The assistant can help without bypassing the flow is described through a fictional but product-grounded state so buyers can understand what changes in the workflow and where the limits are.
Product map
These links are curated for the page rather than generated at random.
Questions
Answers are scoped to repository-verified behavior or intentionally point to current customer documentation when policy facts are not public.
The product surfaces team calendar context according to viewer scope.
Time-off policy and type settings are part of the workspace configuration.
Yes, when Slack actions are enabled and the Slack user maps to an authorized Perelan employee.
No. This page describes schedules and leave context, not a shop-floor time clock.
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
Start with the workflow you want to make calmer, then map the people, records, permissions, and handoffs that make it real.