Skip to main content

Customers

Overview​

A Customer in Atria represents an isolated organization, synonymous with a Company or Tenant.

Customers can either consume services or deliver/sell services as Resellers.

Resellers are customers granted access to create and manage other customers and their services. When a Reseller creates a new customer, the Reseller becomes the parent of that customer. The permission to resell services is granted by provisioning the Reseller Service to the customer.

Resellers can have many sub-customers. It is also possible for a Reseller to have sub-reseller customers. However, each customer can only have one Reseller parent that they are linked to.

Each Reseller can view and manage their own customers, as well as any customers below them in the Atria hierarchy. This includes managing sub-reseller customers.

Root Customer​

The first customer, or "Root Customer," is generally referred to as the Service Provider Customer or Root Reseller. This is the only customer that does not and cannot have a parent customer.

The Root Customer is created automatically as part of the Atria deployment process. The Root Customer cannot be deleted or disabled.

Identifier Attributes​

Each customer in Atria has several identifying attributes:

  1. Display Name: Typically the organization’s name, e.g., "Jones the Baker Ltd". This name can be changed and does not have to be unique.
  2. ShortName: A generated, unique alphanumeric code for the customer, e.g., "JBL" for "Jones the Baker Ltd." The ShortName cannot be changed after creation and is frequently used in automation to generate unique object names when interfacing with multi-tenant systems (e.g., creating a file store, initiating a service, or creating an OU container).
  3. CustomerID: The primary database key of the Atria Customer entity. It is an integer, always unique to the customer, and does not change.
  4. BillingID: A unique identifier used to store a key from a CRM, accounting, or invoicing system of the service provider’s choice.

Domains​

Customers can be associated with one or more domains, e.g., "jonesthebaker.com". These domains can be used to generate usernames, email addresses, or DNS records.

Each domain must be owned by a customer. The first time a domain is added to a customer, that customer becomes the domain owner. However, Atria allows domains to be shared. If the domain is added to another customer, the original owner remains the owner of that domain.

One domain can be marked as the Primary or Default domain for the customer. This primary domain is used as the default for generating user email addresses and other resources.

Extended Properties​

Customers have a standard set of attributes, such as address and contact details. Additional properties can be created through configuration, allowing custom details to be stored for each customer as needed.

All customer attributes are available as part of a provisioning request and can be used in any automation process.

Entra Identity​

Customers can be associated with a Microsoft Entra ID Tenant (formerly Azure AD) through the assignment of the AzureAD service. Once a tenant is associated, users, groups, and licenses can all be managed through the Atria platform.

Active Directory​

Each customer is associated with Active Directory. This association may be either an Organizational Unit (OU) within a shared Active Directory or a direct relationship with a private Active Directory.

When a customer is created, an Active Directory link is established. For a private AD, the customer is directly linked to it; for a shared AD, an OU is created for the customer.