One policy. Every company in the group.
Group structures and shared policies for organizations with subsidiaries. Write a group policy once, share it down the group, and let every company send it to its own people, while you see where each one stands.
Each company keeps its own people, groups and administrators. The group keeps one source for the policies that apply everywhere.
The example group
- Nighthawk GroupGroup parent
- Nighthawk UK LtdSubsidiaryParent
- Nighthawk LondonSubsidiary
- Nighthawk ConsultingSubsidiary
- Nighthawk US Inc.SubsidiaryParent
- Nighthawk New YorkSubsidiary
A parent is any company with companies under it. Nighthawk UK Ltd is both a subsidiary of the group and the parent of London and Consulting.
Click through it yourself
Six steps, from building the structure to publishing a new version. Switch company with "Signed in at" to see what each one sees, and click anything that looks like a button.
Nighthawk Group
Settings · Group structure
Group structure
5 companies below- Nighthawk GroupYour organizationGroup parent
- SubsidiaryParent
- Subsidiary
- Subsidiary
- SubsidiaryParent
- Subsidiary
Each company keeps its own people, groups and policies. Click a company to see its view.
What this gives you
Central control over the policies that apply to the whole group, and local control over everything else.
One structure
Every parent sees the companies under it as a chart in Settings. Each company keeps its own people, groups, policies and administrators.
One source
A shared policy is written once, by the group parent or any parent. Each subsidiary gets a locked copy with the same name, version and document.
As far down as you need
A parent ticks the companies right below it, or any further down. A subsidiary that is a parent can also send a policy it received on to its own.
Sent locally
Each subsidiary decides which of its own groups should confirm, and sends the policy in its own cycles, with its own deadlines and reminders.
Who decides what
The line is the same at every level of the group.
The company that shares the policy
- The policy's name, description and effective date
- The document and every new version of it
- Which companies below it get the policy, at any level
- Withdrawing it, by unticking a company or archiving the policy
Each subsidiary
- Which of its own groups or people should confirm
- When it is sent, in which cycle, with which deadline and reminders
- Its own category, and whether its copy is Draft, Active or Archived
- Whether to send it on to its own subsidiaries
When the parent changes the policy
The copies follow by themselves. Confirmations already made, and the proofs built from them, are kept in every company.
| At the parent | In every subsidiary |
|---|---|
| A new version is uploaded | Every copy gets the new version, with the same version number and document |
| The name or effective date changes | Every copy is updated |
| A company is unticked | Its copy is withdrawn, and so are the copies it sent on |
| The policy is archived | Every copy in the group is withdrawn |
| A subsidiary sends it on | The companies below it get copies of their own, marked as re-shared |
Frequently asked questions
What is a group structure in Policy Confirm?
A chart of the companies in your group. The group parent adds its subsidiaries in Settings, and a subsidiary can add its own. Each company stays its own organization, with its own people, groups, policies and administrators, so a subsidiary never sees another company's people.
How does a shared policy reach the subsidiaries?
The parent creates the policy on the Shared policies tab and ticks the companies that should get it, right below it or further down the chart. When the policy is Active, each ticked company gets a locked copy with the same name, version and document. A subsidiary that has subsidiaries of its own can also send a policy it received on to them.
Can a subsidiary change a shared policy?
No. The content and the document are managed by the company that shared it. The subsidiary chooses who in its own organization should confirm the policy, sends it in its own cycles and decides whether to send it on.
What happens when the parent publishes a new version?
Every copy in the group gets the new version, with the same version number. Each company then sends it to its people in its own cycle, and the parent sees which companies have not started, are in a cycle or are done.
Can a company that already uses Policy Confirm join the group?
Yes. A subsidiary can be a new organization created from the parent's Settings, or one that already uses Policy Confirm. Talk to us and we set up the structure with you.
Set up your group with us
One Standard plan for the group, then as many organizations as you need, from $15 / month each. Tell us how your companies are organized, and we show you the structure with your own names and set it up together.