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

CORE layer 04 of 10

Relationships

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

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

How are they connected?

Relationships are first-class records, not foreign keys hidden in a table. Each one names two parties, a type and a validity period, and can carry its own terms. Authorization reads relationships: a person edits a website because a relationship makes them an editor of that organization. The same model links agents to the people and organizations that own them.

Model

Example entities

  • Relationship
  • Relationship type
  • Role
  • Partnership
  • Customer relationship
  • Supplier relationship
  • Agent ownership
  • Mandate

Contract

Capabilities

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

  • relationship.create→ relationship.created

    Connect two parties with a typed relationship and validity period.

    Privileged role or approval
  • relationship.get

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

  • relationship.list

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

  • relationship.end

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

  • role.grant

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

  • role.revoke

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

  • partner.link

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

  • agent.owner.set→ agent.owner.changed

    Assign the human or organization accountable for an agent.

    Privileged role or approval
The full catalogue

Connections

Relationships

The layers Relationships 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
  • 03

    People

    Who do we work with?

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

    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.

  • People participant

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

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

  • 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.

  • Partners participant

    Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants.

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