KEBS allows you to structure accounts in parent-child hierarchies, reflecting how enterprise clients are organised across subsidiaries, divisions, or regions. Alongside this, each account carries a defined internal team and a stakeholder list that persists across all opportunities and projects linked to it. This article explains how to configure these relationships and what each role means in practice.
Building Parent-Child Account Hierarchies
Give account managers and sales leaders a consolidated view of all commercial activity across a corporate group by connecting subsidiary accounts to a parent, enabling group-level reporting and roll-up visibility.
When creating or editing an account, the Account Info section contains a Has Parent toggle. When this is switched on, a Parent Account lookup field appears directly below it. Search for and select the parent account from this field to establish the hierarchy link.
In the example above, Jifo is being set as a child account under BlueLine Platforms. Once saved, this relationship is visible in the account overview and in the Account Hierarchy section at the bottom of the Overview tab. The hierarchy can span multiple levels, meaning a parent account can itself have a parent.
- 1Open the account you want to make a child record, or start creating a new account.
- 2Scroll to the Account Info section and toggle Has Parent on.
- 3In the Parent Account field that appears, search for and select the parent organisation.
- 4Complete the remaining fields and save the record. The parent-child link is now active.
Account Overview and Lifecycle Status
Give every team member a single pane of glass for an account’s commercial classification, ownership, and current lifecycle status so that no one has to hunt across modules to understand where a client stands.
After an account is saved, all the information entered during creation is displayed in the account’s Overview tab. The overview is divided into the same sections as the creation form: Account Overview, Account Info, Account Managers, and Delivery Stakeholders. All fields are read-only by default and can be edited inline by clicking the edit icon next to each section heading.
Pay close attention to the Account Status field in the Account Info section. This field tracks where the account sits in its commercial lifecycle and directly influences how it appears in pipeline and revenue reports.
| Account Status | What it means |
|---|---|
| Prospect | The organisation has been identified as a potential client but no commercial engagement has started yet. This is the default status when a new account is created. |
| Active | The account has at least one live project or open opportunity and is currently being engaged commercially |
| Inactive | The account had prior engagement but currently has no active work or open deals |
| On Hold | Engagement with the account has been paused, typically due to a client-side decision or an internal review |
The overview also shows the First Opportunity Close Date once a won opportunity is linked to the account, and the Created On date, giving you an audit trail of when the account was first established in KEBS. The Annual Revenue Band field provides a high-level indicator of the client’s revenue scale, used for strategic segmentation.
The Account Team Tab: Internal Stakeholders
Maintain a clear, auditable record of every internal person involved in an account relationship so that ownership is always transparent, handovers are smooth, and the right people are notified when account activity occurs.
The Account Team tab sits in the account navigation bar alongside Overview, Agreement, Address, Notes, Projects, Account Financials, and Audit Log. Inside the Account Team tab, you land on the Stakeholders view, which lists every internal team member currently assigned to this account.
Each row in the stakeholder list shows the following information:
| Column | What it shows |
|---|---|
| AID | The associate ID of the internal team member, linking them to their KEBS associate record |
| Name | The name of the internal team member. A Primary badge indicates this person is the lead owner of the account relationship. |
| The associate’s email address as registered in KEBS | |
| Role | The functional role this person plays on the account, such as Account Manager (AM), Engagement Manager (EM), or Delivery Manager (DM) |
| Assigned By | The KEBS user who added this person to the account team |
| Assigned Date | The date the team member was added to the account |
The stakeholder assigned as the Account Owner (AM) during account creation is automatically populated here with a Primary badge. You can add additional team members to the account using the add-person icon at the top right of the stakeholder list. Each additional member is assigned a role and an assignment date is recorded automatically.
The Past Members tab next to Internal Stakeholders shows a historical log of everyone who was previously on the account team but has since been removed. This preserves accountability and allows managers to see exactly who was responsible for the account at any point in time.
