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

CORE layer 02 of 10

Organizations

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

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

Inside which boundary?

An organization is the unit of ownership in CORE. It owns entities, defines teams and departments, and sets the boundary that permissions and isolation are enforced against. One identity can belong to many organizations with a different role in each. Networks of organizations connect through relationships, never by sharing a database.

Model

Example entities

  • Organization
  • Team
  • Department
  • Business unit
  • Membership
  • Legal entity
  • Organization settings

Contract

Capabilities

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

  • organization.get

    Read an organization and its boundary settings.

    Member of the organization
  • organization.create

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

  • organization.update

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

  • team.create

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

  • team.member.add

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

  • department.create

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

  • membership.invite→ membership.invited

    Invite a person into an organization with a role.

    Privileged role or approval
  • membership.revoke

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

The full catalogue

Connections

Relationships

The layers Organizations 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
  • 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
  • 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

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.

    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.

    organization.get

  • Enterprise participant

    Large organizations running CORE in an isolated deployment with their own identity provider and policies.

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