Access management - 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. One catalog for the tools people can 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. Ask with enough context to decide 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. Route to the right approver 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. Set expectations with service targets 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. Track access and subscriptions beside the person 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. Bring decisions into 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. Use Agents and workflows carefully 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.
Yes. The access app includes a catalog, request flow, ownership, and decision queue.
The catalog can model apps and subscription/access choices where configured.
No broad automatic SaaS provisioning claim is made. Perelan keeps the request, decision, ownership, and handoff visible.
Pending requests are visible through the app and status surfaces according to role.
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.