Evalico’s permission system adapts to any structure, no rigid roles, just clear access rules that make sense.
Model orgs, teams, and reporting lines naturally, permissions inherit where they should.
Decide who can create cycles, edit templates, view results, or manage people, individually or by team.
Feedback, notes, and calibration data stay hidden until explicitly shared or published.
Decide who sees self, peer, upward, and manager feedback, per cycle or per section.
No fixed roles, combine capabilities to fit how your org actually works.
Give team leads, HR, or ops just the access they need to move things forward, nothing more.
Predictable, flexible, and safe by design.
Add teams and reporting lines so visibility and access follow real-world structure.
Grant capabilities like “manage cycles”, “view feedback”, or “edit templates” to specific people or teams.
Start with private-by-default visibility and least-privilege permissions to avoid oversharing.
Change or revoke permissions in seconds. Updates take effect instantly across the org.
Simple enough for small teams, powerful enough for complex orgs.
HR can monitor cycle progress and results without interfering in feedback content.
Leads can manage their teams’ cycles and see direct reports only, nothing more.
Share setup work safely across admins or coordinators without losing control.
Keep feedback phases confidential or anonymized to encourage honesty and fairness.