{"templateId":"markdown","sharedDataIds":{"sidebar":"sidebar-sidebars.yaml"},"props":{"metadata":{"markdoc":{"tagList":[]},"type":"markdown"},"seo":{"title":"Organisational Model","description":"Developer documentation for integrating systems that send messages, plus reporting and operational APIs for platform holders."},"dynamicMarkdocComponents":[],"compilationErrors":[],"ast":{"$$mdtype":"Tag","name":"article","attributes":{},"children":[{"$$mdtype":"Tag","name":"Heading","attributes":{"level":1,"id":"organisational-model","__idx":0},"children":["Organisational Model"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The Digital Postbox Platform is a secure infrastructure for large scale digital message delivery between senders and receivers."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The platform is operated by e-Boks and made available to platform holders within a defined market setup. A platform holder may be e-Boks itself or a partner that owns the digital post service in that market while e-Boks operates the underlying platform."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The platform enables organisations to submit digital messages, manage sender identities, and deliver content to receivers through a consistent and governed structure. Message content is ingested, validated, scanned, encrypted, and processed according to platform rules before delivery."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["This documentation describes how to integrate with the platform using its APIs. It focuses on concepts, data flows, and integration behavior rather than user interface usage."]},{"$$mdtype":"Tag","name":"hr","attributes":{},"children":[]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"organisational-model-1","__idx":1},"children":["Organisational model"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The Digital Postbox Platform is built around a hierarchical organisational model. This model reflects how digital communication is governed and presented within the platform and ensures clear separation of responsibility and access."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The organisational model consists of four core concepts that are used consistently across the platform and its APIs."]},{"$$mdtype":"Tag","name":"hr","attributes":{},"children":[]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"platform-holder","__idx":2},"children":["Platform holder"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The platform holder owns the Digital Postbox service within a market. The platform holder is responsible for:"]},{"$$mdtype":"Tag","name":"ol","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Managing organisation accounts"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Defining governance rules within the market"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Accessing usage and audit data for reporting and billing"]}]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A platform holder may operate multiple organisation accounts within the same platform instance."]},{"$$mdtype":"Tag","name":"hr","attributes":{},"children":[]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"organisation-account","__idx":3},"children":["Organisation account"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["An organisation account represents a legal or operational entity that participates in the platform."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Organisation accounts provide the structural context under which sender identities are created and managed. An organisation account may represent a company, authority, department, or other organisational unit."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Organisation accounts can be structured hierarchically. A parent organisation account may contain one or more sub organisation accounts. Configuration and permissions defined at a higher level apply to subordinate levels."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["To maintain clarity and governance, organisation hierarchies should be kept as flat as possible unless there is a clear organisational need for additional levels."]},{"$$mdtype":"Tag","name":"hr","attributes":{},"children":[]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"sender-identity","__idx":4},"children":["Sender identity"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A sender identity belongs to exactly one organisation account and represents a distinct communication identity."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Sender identities exist to separate communication by purpose, service, or brand while remaining within the same organisation account. Each sender identity defines how messages are presented to receivers and which interactions are allowed."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["An organisation account may contain multiple sender identities."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Sender identities are used when submitting messages and determine how communication appears to receivers."]},{"$$mdtype":"Tag","name":"hr","attributes":{},"children":[]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"receiver","__idx":5},"children":["Receiver"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A receiver is the intended recipient of digital communication delivered through the platform."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Receivers are not part of the organisational hierarchy. They represent the endpoint of communication and interact with messages delivered under a specific sender identity."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Receivers may receive messages from multiple sender identities belonging to different organisation accounts."]},{"$$mdtype":"Tag","name":"hr","attributes":{},"children":[]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"hierarchical-principles","__idx":6},"children":["Hierarchical principles"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The organisational model follows these principles:"]},{"$$mdtype":"Tag","name":"ol","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Organisation accounts may be linked to a parent organisation account"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Sender identities always belong to a single organisation account"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Permissions are inherited from higher levels to lower levels"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Access and responsibility follow organisational boundaries"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["These principles ensure consistent governance and predictable access behavior across the platform."]}]},{"$$mdtype":"Tag","name":"hr","attributes":{},"children":[]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"how-this-model-affects-integrations","__idx":7},"children":["How this model affects integrations"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["When integrating with the platform, senders always act within the context of an organisation account and a sender identity."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["APIs use this model to enforce access control, message ownership, and reporting boundaries. Understanding the organisational model is required before working with message submission, mailbox access, or reporting APIs."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The following sections of this documentation build on these concepts."]}]},"headings":[{"value":"Organisational Model","id":"organisational-model","depth":1},{"value":"Organisational model","id":"organisational-model-1","depth":2},{"value":"Platform holder","id":"platform-holder","depth":3},{"value":"Organisation account","id":"organisation-account","depth":3},{"value":"Sender identity","id":"sender-identity","depth":3},{"value":"Receiver","id":"receiver","depth":3},{"value":"Hierarchical principles","id":"hierarchical-principles","depth":2},{"value":"How this model affects integrations","id":"how-this-model-affects-integrations","depth":2}],"frontmatter":{"title":"Organisational Model","description":"Conceptual understanding on the Organisational Model for the Digital Post Platform.","seo":{"title":"Organisational Model"}},"lastModified":"2026-02-19T09:25:32.000Z","pagePropGetterError":{"message":"","name":""}},"slug":"/introduction/organisational-model","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}