FeaturesOrganizations and roles
Learn and govern

Your whole team, with each client’s data kept apart.

Several hunters, roles with permission per resource, teams and clients. Two-level auditing and a help button on every screen, with isolation between organizations guaranteed at the data layer.

The problem

Why this exists

How it works today

Either the tool is for individual use and the team shares nothing, or it is shared too widely and everyone sees everything. And when a client asks who accessed their candidates’ data, there is no answer.

How it works with EVO

Each organization operates in isolation. Inside it, roles define who sees what, per resource. And every relevant action is recorded, queryable by whoever has permission for it.

How it works

Organizations and roles from the inside

1The team

Roles that go down to the level of the resource.

It is not just administrator and member. You build roles with the permissions that make sense for your operation, and the reach can be the resource itself, the team, or the collaborators.

A person can belong to several organizations, which is common in search firms, and the active organization holds per session. There is no union of permissions across organizations.

Administration · members and roles
CECleyton EstevesAdmin
HRHelena R.Hunter
MAMarina A.Recruiter · SP team
Isolation

69 test cases guarantee that one organization never reads another’s data

Auditing

Every change, security event and sensitive read is recorded

2Accountability

Who did what, and when, is recorded.

Changes, security events and reads of sensitive data are audited. Each organization’s administrator sees their own records; nobody sees another’s.

And every screen in the system has a help button with the documentation for that screen, which cuts training and dependence on whoever already knows how to use it.

The super-administrator creates and administers organizations, but has no operational free pass over client data. To operate, they act inside their own organization.
How EVO learned from you
Aggregate base: 247 screening decisions + 38 flags in the last 90 days.
Top rejection reasons
evidence-weak34%
seniority-below22%
skills-mismatch18%
salary-likely-above13%
Top shortlist reasons
trajectory-strong28%
evidence-strong19%
skills-strong17%
culture-fit-strong12%
Real outcome × your decisions

"Of your shortlists based on trajectory, 71% became hires that lasted past 90 days: the pattern that looked like bias is delivering. Shortlists based on evidence converted at only 45%."

Base: 17 closed processes with a recorded outcome · N is still small, read it as a trend.
Under the hood

The isolation is structural, and proven on every change

In a product where several clients coexist, "we trust the developer remembered to filter" is not a guarantee. Here the guarantee lives in the architecture and in CI.

6969 isolation test cases running against a real database, with two mirrored organizations
2 bugsThat suite has already found two real leaks between organizations before any client saw them
24The organization scope is injected automatically into 24 data models
lintUsing the unscoped database client in the application and interface layers breaks the build
404Access to another organization’s data returns "does not exist", never reveals that something is there
ruleA new feature without an isolation test does not ship: it is a repository rule, not a recommendation

Adding up the product’s suites, there are more than 2,400 automated test cases, 1,377 of them over the pure business rules, with no database and no interface.

What comes next

How it fits into the rest of the journey

Bring a role that is hard to fill

It takes a real role to see EVO work, not a canned example.

Start using it