BUSINESS SERVICES use case

Shape operational data around the business you actually run

Service organizations do not all manage the same entities or fields. One may organize clients and locations; another may organize portfolios, projects and service assets. Akeye starts with reusable building blocks instead of one fixed industry table.

Groups provide the wider grouping, units represent the operational entities inside it, and parameter schemas add organization-specific fields. Activities, contacts, Documents and relationships then connect day-to-day work to that structure.

01

Build the model in layers

Start with stable business entities, then add the data and work that belongs to them.

  1. 01

    Choose the groups

    Represent the major groups the organization operates, such as accounts, portfolios, departments or service areas.

  2. 02

    Define units

    Add the people, locations, assets, projects or other entities managed inside those groups.

  3. 03

    Configure relevant fields

    Use active parameter schemas to define typed values and organization-specific data entry.

  4. 04

    Connect operational work

    Relate Activities, contacts, Documents and other supported records to the units where they have meaning.

02

Reusable building blocks

The model stays flexible while preserving explicit organization and relation boundaries.

Two-level unit structure

Groups and units provide a shared hierarchy for different operating models.

Configurable parameters

Schemas define supported fields, types, grouping, ordering and whether a value is required in the relevant UI.

Relations instead of copies

Operational records can point to the units they concern rather than duplicating their identity in free text.

Work in context

Activities, contacts, Documents and communication remain meaningful because they are attached to the business structure.

03

Flexibility with governance

A flexible model still needs deliberate configuration and clear ownership.

  • Akeye does not infer the correct schema or business taxonomy automatically.
  • It is not an unrestricted database builder; supported entity, field and relation types remain defined by the product.
  • Configuration should use canonical keys and active schemas rather than duplicating the same concept under several names.

FAQ

Flexible data model FAQ

Answers about units, parameters and operational relations.

What is the difference between a group and a unit?

A group brings related units together, such as a client with its locations or projects. Each unit is an individual item you manage.

Can administrators add organization-specific fields?

Yes. Administrators can configure additional fields for the information their organization needs, using the available field types.

Does flexibility change who can access information?

No. Information stays within its organization, and people can only access it according to their permissions.

Describe your operational structure

Bring the entities, relationships and fields your team currently manages, and we can assess how they map to Akeye’s existing building blocks.

Contact us