Skip to main content
Group & entities

Shared and local catalogues and settings

Decide what the group shares with entities and what each entity keeps for itself.

Written By Karl

Last updated About 9 hours ago

If your organisation uses entities, this article explains how to decide what the group shares with entities and what each entity keeps for itself.

Sharing rules

Go to Settings → Organization → Entities → Sharing in the Group view. For each catalogue, choose one of:

  • Shared: the group's rows are used by every entity.

  • Local: each entity keeps its own rows, which are visible only inside that entity.

  • Shared + local: entities use the group's rows and can also add their own.

Catalogue

Default

Job architecture (levels, grades, paths), job families, evaluation frameworks, custom fields

Always shared

Positions, pay components and benefits, work schedules, pay rationale tags, skills

Shared + local

Organization units, worksites, pay bands

Local

You can't make a catalogue Shared while entities still own rows in it. Evenpay names those rows, so you can move or remove them first.

Owner column

Once you have a second entity, catalogue lists show an Owner column. A row you can't change in your current view is read-only and marked with a lock. When you create a row in the Group view, choose its Owner:

  • the group's rows are shared with every entity;

  • an entity's rows stay inside that entity.

An entity sees the group's rows, the rows of the entities above it, and its own rows. It never sees a sibling entity's rows.

Settings per entity

When you switch to an entity's view, settings pages show that entity's values, and changes apply to that entity only. An entity can have its own:

  • currency (set on the entity itself, see Setting up your entities);

  • work schedule;

  • pay band settings;

  • pay gap thresholds;

  • offer policy.

Anything an entity doesn't set is inherited from the group.

Some settings always belong to the group and are read-only in an entity's view: security, branding, email delivery, Early Access, keywords, pay rationale tags, pay information request settings and pay information reminders. The group's pay gap convention is locked by default, so every entity calculates gaps the same way.

Privacy floor

An entity can require larger groups than the group does before figures are shown, but never smaller ones. Where the group and the entity have different floors, the stricter one always applies.

Was this helpful?

Still need help? Share an idea