Organisations
An organisation is how you split your workforce into groups. Each worker belongs to an organisation — typically a site, business unit, legal entity, or region — and that grouping is what lets you see and report on compliance one part of the business at a time, rather than as one undivided list.
If a worker is a person and their credentials are what they carry, an organisation is the part of your business that worker sits in.
Why organisations matter
Splitting workers into organisations gives you three things:
- Compliance reporting per organisation. You can see your compliance position for each organisation on its own — how many workers are compliant, at risk, or non-compliant — instead of only across everyone at once.
- The right people see the right workers. Access can be scoped by organisation, so a manager who looks after one site sees the workers and compliance for that site, not the whole company.
- A link to your external systems. When you set up automated checking, organisations can be mapped to the matching organisation in an external provider's system, so the right workers are checked under the right account.
Every worker belongs to one
When you add a worker, choosing an organisation is required. If the organisation you need doesn't exist yet, you can create it on the spot — start typing its name and pick + Create, then carry on. To create one without adding a worker, see Create an organisation. Over time this builds up the set of organisations you can group, filter, and report by.
The choice sticks: there's no organisation field on Edit worker, because a worker's organisation scopes their whole record rather than describing it. When someone transfers between sites, see Moving a worker to another organisation.
Create an organisation
You don't need a worker to create an organisation. Set one up ahead of time when you want its verification sources and user access ready before the first worker arrives.
Organisations are managed on the Organisations page. It isn't in the menu yet — go to /domains on your Oho address (for example https://yourcompany.weareoho.com/domains) and bookmark it.
- Click Create.
- Enter a Name. It's the only required field, and it must be unique within its parent.
- Optionally add a Description and a Parent Organisation (see below).
- Click Save.
Super Admins, Admins and Managers can create organisations. Observers can't — the Create button still shows, but saving fails with an authorisation error.
Advanced Options → Custom Id sets the organisation's permanent internal id instead of a random one. You only need it if an integration or Oho support has asked for a specific id. It can't contain spaces, commas, brackets or colons, and it can't be changed later. If you type a Custom Id and then clear it, Save can stay greyed out — cancel and start again.
What Parent Organisation does
A parent nests one organisation under another on the Organisations page. That's all it does: access and reporting don't roll up. Someone given access to the parent doesn't see the child's workers unless they're given the child too, and the Compliance Overview reports each organisation on its own.
After you create one
A new organisation starts out covered by nothing. Before its first worker arrives:
- Add it to each verification source that should check its workers — NCC police checks, NSW Working With Children, QLD Blue Card and the other sources that sign in on your behalf only check workers in the organisations listed on the source. See Add a verification source.
- Give the right people access with Switch Organisation — Super Admins see everything, but everyone else only sees the organisations they've been assigned. See Manage users.
Reporting on compliance
The Compliance Overview is where organisations earn their keep. You can:
- view the headline compliance numbers for everyone,
- filter to a single organisation to see just that group's position, and
- expand a per-organisation breakdown that lists each organisation with its worker count and how many are compliant, at risk, or non-compliant.
The same breakdown can be exported to a spreadsheet, with a row per organisation, so you can share a compliance snapshot with the people responsible for each part of the business.
Who sees what
Access is scoped by organisation for everyone except Super Admins. Admins, Managers and Observers are each assigned the organisations they're responsible for when they're invited, and see only those — an Admin is not tenant-wide. For a full breakdown of the roles and how to scope people, see Roles & access.
Connecting to external systems
Some checks run against an external provider that has its own idea of which organisation a worker belongs to. When you set up automated checking under Verification Sources, you can map each of your Oho organisations to the matching organisation on the provider's side, so workers are checked under the correct account.