Skip to content
Resorcerer Docs

People and attributes

People and the attributes that describe them live at the organization level, not inside any one model. Add someone once and they’re available to every model; rename a role and the change is reflected everywhere it’s used.

People

Section titled “People”

A person is a record of somebody who could occupy a position. Adding a person to Resorcerer does not give them a login — that’s invitation to the workspace, which is separate.

Field Notes
Name Required.
Email Required, and the key used to recognize someone on re-import.
Title Free-text job title, as distinct from the structured Role below.
Role, Level, Location, Company The person’s own attributes.
Department Free-text grouping.
Manager Another person. A people-level reporting line, separate from the slot-level one inside a model.
Start / end date When they join and leave the organization.
Photo An image URL, used in the org chart and people views.

People are added by hand, imported from a CSV, or provisioned from your identity provider where that’s configured.

Deleting a person is reversible — they go to the trash — and any slot they occupied simply becomes vacant. The structure you planned survives the person leaving.

People versus slots

Section titled “People versus slots”

It’s worth being precise about the difference, because both carry the same four attributes:

  • A person’s attributes describe them: Priya is a Senior Engineer in London.
  • A slot’s attributes describe the position: this is a Senior Engineer post in London, whoever fills it.

They’re allowed to disagree, and the disagreement is often the interesting part — a person acting up into a more senior post, say. The Problems view lists mismatches so you can decide whether each one is deliberate.

Attributes

Section titled “Attributes”

Four attributes describe both people and slots. All are optional, all are defined by you, and all are used for filtering, grouping in the breakdown views, and matching cost profiles.

Roles

Section titled “Roles”

The job function — Engineer, Designer, Product Manager. A role can also carry a category, which groups related roles together so the breakdown views can report at either granularity.

Levels

Section titled “Levels”

The seniority tier — Junior, Mid, Senior, Lead. Each level has a rank, a number that sets its order. Rank is what makes levels sort meaningfully rather than alphabetically, so give them ranks in the order you’d read them.

Locations

Section titled “Locations”

The site or working arrangement — London, NYC Office, Remote.

Companies

Section titled “Companies”

The employer. Each company is marked as internal or contractor, which is what lets the breakdown views separate employees from contingent workers and report on each.

Unit types

Section titled “Unit types”

Unit types classify units rather than people — Department, Team, Squad. Each carries a colour used in the tree and the visualizations.

Deleting an attribute

Section titled “Deleting an attribute”

Resorcerer checks what an attribute is being used by before it lets it go:

Situation What happens
Not used anywhere Deleted straight away.
Assigned to people or slots You’re warned how many, and can go ahead — those records simply lose that attribute.
Used by a cost profile Blocked. Remove it from the cost profile first, so costing can’t silently change underneath you.
Section titled “Related”