IntegrationSlack integrationAvailable
Make a decision in Slack. Keep the authority and record in Perelan.
Verified integration behavior only. External tools remain their own systems of record where applicable.
Operational flow
Start with identity and setup, then follow the data direction, permission check, source record, and fallback state.
Perelan connects the Slack workspace, links Slack users to Perelan employees, scans configured recruiting channels where enabled, imports a resume with the connected authorization, sends a candidate card, verifies the Slack request signature on action, rechecks recruiting permission as the linked employee, changes the source candidate record, and rewrites the Slack message with buttons removed.
This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.
This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.
This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.
Runtime path
Relevant product paths
Controls and boundaries
Yes. Configured channel import can scan messages for PDF files, download permitted private files with the connected Slack authorization, parse the resume, and create or enrich candidates.
No. The Slack user must resolve to a linked Perelan employee and pass recruiting authorization.
No. It is a traceable candidate decision by a linked authorized user, not an aggregate vote tally.
No. Perelan changes the source candidate record and rewrites the Slack card to show the outcome.
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.