Share companies and personnel records with child sites
Open child sites can show eligible companies and personnel records from ancestor sites. Sharing is controlled by Personnel settings defaults, each record’s Share with Child Sites setting, and the child site’s Cascade Mode.
Before records can inherit
A company or personnel record appears as inherited on a child site only when all of these are true:
The child site’s Cascade Mode is Open.
The ancestor record is eligible under the parent’s share-down default or an explicit Share override.
The viewer can access the record under normal Personnel permissions on the owning ancestor site.
Sealed child sites show only their own companies and personnel records. Ownership always stays with the site that owns the record. For Open and Sealed site behaviour, see Cascade Mode for sites.
Set the site share-down defaults
Parent sites with child sites set both defaults under Personnel Settings.
Go to Settings > Personnel.
Open the Options tab.
Turn Share Personnel Records with Child Sites on or off.
Turn Share Companies with Child Sites on or off.
Click Save Changes.
When a default is on, records that follow the site default may appear in open child sites. Individual records can override the default. The controls appear when cascade is available and the site has child sites. Changing these options requires Site Manager or Site Admin access.
Both share-down defaults are on unless you turn them off.
Control sharing on a company
On a parent site with child sites, set Share with Child Sites when you create or edit a company.
Go to People > Companies.
Create a company or open an existing company and edit it.
Set Share with Child Sites to one of:
Use the Site Default (on) or Use the Site Default (off) — follow the Companies site default. The label shows whether that default is currently on or off.
Share — this company may appear in open child sites.
Don't Share — this company does not cascade, even if the site default is on.
Save the company.
New companies start on Use the Site Default. The control appears only when cascade is available and the site has child sites. You need the Manager or Admin role for the Personnel module to create and edit companies. For day-to-day company steps, see Adding and managing company details.
Control sharing on a personnel record
On a parent site with child sites, set Share with Child Sites on the person’s personnel record.
Go to People and open the person.
On the personnel record, set Share with Child Sites to one of:
Use the Site Default (on) or Use the Site Default (off) — follow the Personnel Records site default. The label shows whether that default is currently on or off.
Share — this personnel record may appear in open child sites.
Don't Share — this personnel record does not cascade, even if the site default is on.
Save the share setting.
The control appears only on own-site personnel records when cascade is available and the site has child sites. It does not appear on inherited records. You need the Manager or Admin role for the Personnel module to edit personnel records. For creating records, see Add a personnel record.
What child-site users can do with inherited companies
Inherited companies are read-only in the child site. Ownership and edits stay on the owning ancestor site.
Action | On inherited companies |
|---|---|
View company details, contacts, addresses, registrations, links, files, and available blocks | Yes, when access rules on the owning site allow |
Edit company details | No |
Add, change, or remove blocks, contacts, notes, or attachments | No |
Archive, reactivate, or delete | No |
Link or unlink from child-owned records | No |
Use the company in child-site selectors and linking flows | No — selectors offer own-site companies only |
Inherited rows are labelled Inherited from followed by the ancestor site name.
What child-site users can do with inherited personnel records
Inherited personnel records are read-only in the child site. Ownership and edits stay on the owning ancestor site.
Action | On inherited personnel records |
|---|---|
View available details and blocks | Yes, when access rules on the owning site allow |
View sensitive blocks | Yes, only with sensitive-data access on the owning site |
Edit the record, blocks, attachments, or access settings | No |
Change integration data | No |
Use the record in child-site selectors and linking flows | No — selectors offer own-site records only |
Inherited rows are labelled Inherited from followed by the ancestor site name.
The People list shows one primary personnel row per person. An own-site personnel record takes precedence over an inherited record for the same person. If there is no own-site record, the nearest eligible ancestor record is shown.
Filter own and inherited records
On an open child site with a parent, the People and Companies lists can show an Ownership filter when cascade is available.
All People or All Companies — own records plus eligible inherited records (default).
This Site Only — records owned by the active site.
Inherited Only — eligible inherited records only.
The filter does not appear on sealed sites or sites without a parent.
People exports
People exports can include eligible inherited personnel rows. The Personnel Record Source column shows This Site for own-site records, or Inherited from followed by the ancestor site name for inherited records.
When inherited records stop appearing
A company or personnel record is available on a child site only while it remains eligible. If the child is sealed, the parent turns off sharing, or the record is set to Don't Share, it does not appear as inherited content for that child.
Related guides
Cascade Mode for sites — Open vs Sealed and where to change the site setting.
Adding and managing company details — notes, blocks, and day-to-day company edits on owned records.
Add a personnel record — create personnel records on the owning site.
Personnel roles and access — Member, Manager, and Admin roles for Personnel.
Share documents with child sites — Documents share-down defaults and inherited library behaviour.
Share risks content with child sites — Risks content under cascade.