Multiple accounts

Single and parent/child accounts

Overview

You will always have a single (parent) account when you complete your registration. But if a single account does not meet your needs, you can create and configure multiple accounts with KORE.

You can create multiple single accounts or, based on your needs, create a parent/child configuration.

Parent/child account management provides a four-level hierarchical configuration. Accounts can have both parent and child roles, as shown below.

parent/child chart

Regardless of its type, every account is assigned a unique identifier known as the account ID. The ID is used throughout our documentation, user interface (UI), and application programming interfaces (APIs).

Relationship tree

The option is available on multiple pages. Select to see the hierarchy of the parent/child structure. Select the expand > icon to open all levels.

The tree will list only the accounts you have access to.

Folder type	Description
	The account has child accounts.
	The account does not have child accounts.

Export list

The export list option will create and download a CSV file automatically to your current device.

Parent account

Your initial account will always be the parent account, which is the billable account that consolidates charges from all associated child accounts, if applicable. The parent account is the primary account affiliated with KORE.

Each parent account has a separate invoice, payment methods, user base, API credentials, and resources. For example, the SIMs in Account 1 have no connection to the SIMs in Account 2, even if both accounts belong to the same owner, and both Account 1 and Account 2 will receive an invoice.

A parent account will always have one owner who can invite additional users. Any user with any role can create an account, which they will be automatically assigned as the owner. A user can own multiple parent accounts and switch between them easily.

An owner can transfer ownership of an account to another user at a later time.

Child account

A child account allows you to allocate your resources to various subaccounts. Some users do this to organize resources by end customer, department, region, or business unit. Ultimately, how you structure your accounts and resources is up to you.

A child account must always be associated with a parent account. Child accounts are not billable separately, and a root-level parent is always associated with any hierarchy invoicing.

All users with access to the parent account will inherit the same set of permissions in the child accounts. A user can move resources from a parent account to a child account, which means these resources will now be managed from the destination child account.

Any charges generated from a child account will be aggregated under the parent account at the rates agreed upon with KORE for the parent account.

Account hierarchy examples

Default

In this example (the default behavior), the user is satisfied with a single account they created during registration.

Parent Account 1 (Owner) < Invoiced

Multiple child accounts

You wish to segregate your resources per child account for each end customer and report on each end customer based on the unique account identifier for each child's account. Each resource, such as a SIM, will identify the child and parent accounts to which it belongs.

Billing

You will receive a single invoice with the charges rolled up from each child account (A, B, C) to Account 1.

Parent Account 1 (Owner) < Invoiced
│
├── Child Account A < Charges rolled up to parent account 1
├── Child Account B < Charges rolled up to parent account 1
└── Child Account C < Charges rolled up to parent account 1

Multiple parent accounts

You may wish to have different invoices billed to other addresses.

Billing

Each single-parent account is considered a different hierarchy, and each will receive an invoice to the same user (owner).

Parent Account 1 (Owner) < Invoiced

Parent Account 2 (Owner) < Invoiced

Combination of multiple parent and child accounts

Parent Account 1 (Owner) < Invoiced
│
├── Child Account A < Charges rolled up to parent account 1
├── Child Account B < Charges rolled up to parent account 1

Parent Account 2 (Owner) < Invoiced
│
├── Child Account D < Charges rolled up to parent account 2
├── Child Account E < Charges rolled up to parent account 2
└── Child Account F < Charges rolled up to parent account 2