Recruiting - 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. Publish a clear role and application path 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. Turn a resume into usable 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. A pipeline with the work attached 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. Triage candidates 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. Import from the conversation 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. Convert once, continue in Core HR 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. Permissions follow the candidate data 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 recruiting service includes public role/application routes and form handling.
Yes. The Slack/recruiting services can scan configured channels for PDF resumes and import candidates using the connected authorization.
No. Resume parsing creates context for people to review; hiring decisions remain human and permission-checked.
The recruiting service calls the people service to create the employee record while carrying over relevant candidate context.
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.