Accounts
Accounts are billable entities that represent a container for business transactions, including Entitlements, Orders, or Workflow Invocations. Accounts typically originate upstream from customer transactions, with information relating to the customer (e.g., account name) and the transaction (e.g., Bill To address) details. Once a customer has transacted under an account, the purchased product and any Users managing or receiving access to the product are typically associated with the Account. That access can trigger workflows such as TID’s Managed Users onboarding workflow. Accounts also serve as the fundamental entities for tenancy. Account context for all identities will be provided in JWT. This ensures enabling seamless integration and authentication across various systems and applications.
Accounts management in IAM require specific privileges for usage. Requests for these privileges must be submitted as support tickets.
Sources of Account Data
Section titled “Sources of Account Data”IAM ingests Accounts from privileged systems of records whose workflows and data have been vetted to ensure IAM stores Account Data that Trimble can rely on. For example, rep-based workflows produce customer Account data sourced from salespeople or dealers through systems like Salesforce and Oracle. Direct-to-consumer sales interfaces also create accounts and produce data updates directly to IAM. Such systems are explicitly authorized to generate accounts in IAM.
Account Types
Section titled “Account Types”Accounts are classified into two categories: their type and their customer type. Type represents the B2B quality of the account, with options of Customer, Distributor, Reseller, or Dealer. The Customer type is a further breakdown of the type selection, indicating the relative size of the customer that owns the account. These are typically based on the end-user volume of the account and can be selected from Individual, Organization, or Enterprise.
Account Schema
Section titled “Account Schema”Accounts are comprised of the basic information about a Customer, their transactions, and where the account is sourced from. Furthermore, accounts may contain address information and contact information beyond the primary information. The schema can be accessed in the API Reference for accounts and addresses.
This schema is subject to evolve as Trimble moves toward an Account Master model, where all businesses, and their customer Accounts, flow through IAM.
User Access Management through Account Roles
Section titled “User Access Management through Account Roles”Access to Accounts and their assets are defined by roles an identity can occupy on an account. These roles and their permissions include standardized account roles and custom roles defined by a business unit. Every User to Account relationship leverages standard roles, but Users can also be assigned additional custom roles.
Standardized Roles and Permissions
Section titled “Standardized Roles and Permissions”- Account Owner: The singular Owner of the Account.
- Secondary Account Owner: Additional owners on the account.
- Admin: Administrator of the account that can maintain the account for the customer, including but not limited to, its end-users to be licensed for product usage.
- End User: A user with no management privileges.
For more information on Roles and Permissions, see the Roles section and Permissions section.
Account Context for all Identities
Section titled “Account Context for all Identities”By storing Trimble’s customer Account data alongside authenticated identities (e.g., Users, Applications, and Devices), IAM can associate all identities to an account. Such relationships allow Trimble businesses to derive an account context for all customer interactions across our ecosystem. This can be further leveraged for revenue-generating billing opportunities and better reporting of customer product usage.
Modularity via Organizations and Account Linking
Section titled “Modularity via Organizations and Account Linking”IAM enables modularity through customer Organizations and Billable Accounts. Today, the Billable Account is the tenant for all customer data and administrative management. The same customer’s data is often spread across multiple Accounts living in different systems, creating a fragmented management experience. By introducing Organizations and linked Accounts, not only can customer Accounts be associated with a company profile, but customers and partners can maintain their assets in a way that reflects their organizational structure.
For more information on Organizations, see the Organizations section.
Dealer-Customer Relationships
Section titled “Dealer-Customer Relationships”A dealer account can establish a doingBusinessWith relationship with a customer account, so it can manage the customer’s account and, once opted in, view and support the customer’s users, devices, and shipping addresses on the customer’s behalf.
Establishing this relationship is a two-phase process: the dealer first creates the account-to-account relation, then requests an opt-in that the customer must approve (unless the customer self-initiates it, in which case it is committed immediately). The customer can view, approve, reject, or revoke dealer access at any time through the managedBy endpoints.
For the full step-by-step workflow, request/response examples, and the opt-in status lifecycle, see Dealer-Customer Opt-In Workflow.