Organizations and Sub-Organizations

Follow

The Harver Platform provides a structured, hierarchical approach to managing customer accounts, locations, and vacancies. Organizations entity/capability allows us to better structure customer accounts and provide additional functionality to both internal and external users.

Please note: All company names mentioned in this article and on screenshots are examples and entirely fictional.

In this article:

  1. Key Components of the Account Hierarchy
    1. Account: The foundation
    2. Organizations & Sub-Organizations: Grouping accounts
    3. Sub-Organizations: Deeper structuring for Reseller use cases
  2. Accessing Organizations
  3. Organization Tree and Search
  4. Sub-Organizations
  5. Organization Users and Permissions
    1. Organization permission levels
    2. Organization Viewers
    3. Organization Admins
  6. Sub-Organizations and Cascading Permissions
    1. Elevating Access (to a higher level)
    2. Downgrading Access (to a lower level)

Key Components of the Account Hierarchy

Account: The foundation

At the core of our system is the customer account. This is not a user account but rather an entity that stores all configurations and data related to a customer.

  • A customer account can represent a single customer organization or a subset of a larger organization.

  • It holds the customer’s settings, candidate data, and assessment configurations.

Organizations & Sub-Organizations: Grouping accounts

For customers with complex organizational structures, accounts can be grouped into organizations.

  • An organization is a collection of customer accounts

  • Organizations can also have sub-organizations, allowing for deeper structuring when needed.

Sub-Organizations: Deeper structuring for Reseller use cases

  • A sub-organization is an organization under another organization.

  • Sub-organizations can have their own customer accounts and even their own sub-organizations.

  • Our platform allows for up to four levels of sub-organizations if necessary.

  • This feature is primarily designed for reseller scenarios, where an organization resells the platform to smaller entities that manage their own customers.

Each level can maintain separate configurations, ensuring that sub-organizations can operate independently while still being part of a structured hierarchy.

ba6c733c-40b0-4eb9-9aa0-96dd16711a4b.png

Accessing Organizations

Users who have permission to manage Organizations can access this feature directly from the top navigation menu after logging in to the Harver Platform.

From the Accounts List page, select Organizations in the top menu to open the feature. This will take you to the main Organizations dashboard, where you can view and manage all associated client organizations.

After opening the Organizations page, users with access will see a tree structure representing the hierarchy of organizations and accounts they have permission to view.

Access permissions in Harver are cascading, meaning that users can automatically access all entities and sub-levels beneath the organization they are assigned to. For example, if a user has access to a parent organization, they will also be able to view and manage all its child organizations.

When an Organization or Account is selected in the tree view, a Quick Details panel appears on the left side of the screen.

This panel provides an at-a-glance summary of key information related to the selected item, allowing users to quickly review details without leaving the main hierarchy view.

The Search function allows users to find any Organization or Account that matches the entered search criteria.

Search results are case-insensitive, meaning users can enter text in any combination of upper or lower case and still receive matching results.

The Search function requires a minimum of three characters to return results.

When a match is found, the system displays the matching Organization or Account, along with the full hierarchical path leading to it. This helps users easily identify where the item is located within the overall organization structure.

  1. Navigation back to the tree view

  2. Breadcrumb navigation

  3. Quick details overview

  4. Sub-Organizations management

  5. Account management

  6. Organization users

Sub-Organizations

Sub-Organizations can be created by Organization Admins.

Organizations have cascading permissions, which means that any Organization Admin can create accounts in the Organization they got directly access to as well as all sub-organizations under that.

Once an Organization is created, clicking on it in the list view open it on the overview page.

  1. Navigation back to the parent Organization

  2. Breadcrumb navigation shows the structure

Sub-Organizations functionally behave the same way as their parent organization.

Organization Users and Permissions

Organization permission levels

Organizations have 2 permissions levels:

  • Organization Admin

  • Organization Viewer

Organization Viewers

Typically customers who have a dedicated Organization with multiple accounts will be added to their Organizations as an Organization Viewer. They have limited capability, will see only their own Organization and Account within that, and will not be able to add sub-organizations or create additional accounts.

For Non-super Admin users (Account Managers, Integration Specialists, etc) we recommend granting Organization Viewer access, this way they can see customers but cannot create new entities and can’t access accounts they were not assigned to.

Organization Admins

Resellers and customers who are allowed to create Sub-Organizations and Accounts within their Organization will be granted Organization Admin access rights.

Sub-Organizations and Cascading Permissions

Organizations are designed to be nestable. so we can create more complex structures and aid the account hierarchy and support reseller structures.

We always have a Top-Level Organization and we will soon add Sub-Organizations. A top Level Organization can have up to 4 sub-organization levels.

The permissions are designed to cascade downwards in the hierarchy. For example, taking the structure from the image above:

  • A user granted Organization Admin access to the Top-level Organization “Global HR SAAS Reseller“ has the same access level automatically granted to all Sub-Organizations.

  • A user granted Organization Viewer access to “HR SaaS reseller for Paris”, has the same access to the sub-Organization “Recruitment Agency“ but has no access and cannot see the higher level Organizations above “HR SaaS reseller for Paris”.

Elevating Access (to a higher level)

If a user needs access to a higher-level Organization:

  1. Remove the user from their current Sub-organization.

  2. Re-add them at the higher-level Organization.

    Their new permissions will cascade down automatically.

Downgrading Access (to a lower level)

If a user should have reduced access:

  1. Remove the user from the current Organization level.

  2. Re-add them at the desired lower-level Sub-organization.

    Permissions will again cascade down automatically.

 
Was this article helpful?
1 out of 1 found this helpful