Skip to content
2finity.com
2finity.com
2finity.devSign in

CORE layer 03 of 10

People

Customers, employees, professionals, suppliers and leads: the people an organization works with, as one record each.

2finity CORE and the interfaces and participants connected to it
COREWebsiteApplicationsChatAgentsPeopleCompaniesPartnersEnterprise
CORE
The shared operating layer. Ten layers: Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication, Data.
Website (interface)
Public sites and portals that read content and catalog data and submit forms through CORE. Uses the Identity, Knowledge, Commerce and Data layers. Example capabilities: page.get, catalog.list, form.submit.
Applications (interface)
Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions. Uses the Identity, Organizations, People, Workflows and Data layers. Example capabilities: customer.get, workflow.start, approval.decide.
Chat (interface)
2finity.chat and other conversational interfaces: language resolved to capabilities, with approval. Uses the Identity, Knowledge, Workflows, Finance and Communication layers. Example capabilities: site.content.update, invoice.create, permission.grant.
Agents (interface)
Actors with their own identity, an owner and scoped permissions; every action leaves an audit event. Uses the Identity, Knowledge, Workflows and Communication layers. Example capabilities: site.publish, deployment.rollback, workflow.start.
People (participant)
Humans in any context: professional, employee, customer or supplier, with one identity throughout. Uses the Identity, People, Relationships and Communication layers. Example capabilities: customer.get, permission.grant, message.send.
Companies (participant)
Organizations that own their data, run their workflows and decide who and what may act inside them. Uses the Organizations, People, Relationships, Commerce and Finance layers. Example capabilities: organization.get, invoice.create, order.update.
Partners (participant)
Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants. Uses the Identity, Relationships, Commerce and Data layers. Example capabilities: catalog.product.get, order.update, permission.grant.
Enterprise (participant)
Large organizations running CORE in an isolated deployment with their own identity provider and policies. Uses the Identity, Organizations, Workflows, Finance and Data layers. Example capabilities: permission.grant, deployment.publish, workflow.start.

Scope

What it holds

Who do we work with?

People are the humans an organization knows about, independent of how they arrived. A customer, an employee and a supplier contact are the same kind of record with different relationships attached. When a person also has an identity, the two are linked, so a customer who later joins as an employee is still one person. Leads are people whose relationship is not confirmed yet.

Model

Example entities

  • Person
  • Customer
  • Employee
  • Professional
  • Supplier contact
  • Lead
  • Contact detail
  • Address

Contract

Capabilities

Every action on this layer is a named capability with a permission check and, where something changes, an event.

  • person.get

    Named in the layer model; not yet described in the catalogue.

  • person.create

    Named in the layer model; not yet described in the catalogue.

  • person.update

    Named in the layer model; not yet described in the catalogue.

  • person.merge

    Named in the layer model; not yet described in the catalogue.

  • customer.get

    Read a customer record with its relationships to the organization.

    Member of the organization
  • lead.create

    Named in the layer model; not yet described in the catalogue.

  • lead.qualify

    Named in the layer model; not yet described in the catalogue.

  • lead.list

    List leads, filterable by source, region and period.

    Member of the organization
The full catalogue

Connections

Relationships

The layers People reads from and writes to most often.

  • 01

    Identity

    Who or what is acting?

    Who or what is acting: humans, agents and service identities, known once and recognized in every context.

    Open layer
  • 02

    Organizations

    Inside which boundary?

    Companies, teams, departments and business units: the boundaries inside which people, data and permissions live.

    Open layer
  • 04

    Relationships

    How are they connected?

    Connections between people, organizations, roles and agents: who is a customer, employee, supplier, partner or owner of whom.

    Open layer
  • 09

    Communication

    How do we talk?

    Messages, conversations, notifications and threads between people, agents and organizations.

    Open layer

Consumers

How interfaces use it

The interfaces and participants on the CORE graph that read or write this layer, with the capabilities of this layer they name.

  • Applications interface

    Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions.

    customer.get

  • People participant

    Humans in any context: professional, employee, customer or supplier, with one identity throughout.

    customer.get

  • Companies participant

    Organizations that own their data, run their workflows and decide who and what may act inside them.

    Uses the layer; its featured capabilities belong to other layers.