Docs

Search and contents

Enterprises, tenancy and organization workspaces

One product serves many organizations; a single sign-in never means holding all of any organization's data. Organization, permission and data boundaries come first; deeper enterprise collaboration follows step by step.

In developmentNot availableVerified

Enterprises, tenancy and organization workspaces diagram (A13) (open full-size figure)
MYRILUM architecture map v2.2 · A13 (public edition). Labels are in Chinese; every element is listed in English below. Select the diagram to open it at full size.

What this map shows

This is MYRILUM's target architecture. It does not mean everything on the map is live; whether a capability can be used today is stated in “Current availability”.

One product can serve many organizations; a single sign-in never means owning all of any organization's data.

First get organization, permission and data boundaries right, then deepen enterprise collaboration step by step.

Organizations and identity

OrganizationLegal and business details are kept apart from platform identifiers
Tenant boundaryOwns data, access, keys and run policies
WorkspaceScope of projects, materials, members and organization knowledge
Members and rolesInvitation, joining, permissions, revocation and leaving

Enterprise work and resources

Projects and deliveryTasks, approvals, artifacts, evidence, acceptance and archiving
Budgets and procurementDepartment and project credits; procurement kept apart from authorization
Organization knowledgeAuthorized import, permissions, indexing, updates and deletion
Enterprise system connectionsCRM, ERP and other systems connect as needed through connectors

Cross-organization collaboration by explicit sharing

Sharing requestResource, purpose, receiving organization, actions and time limit
Approval and grantThe data side and the executing side each confirm their responsibilities
Checked again at run timeMember, resource, purpose, permission and validity
Revocation and completionStops new access; handles copies, caches and handoffs

The enterprise lifecycle

OnboardingContract, region, identity and data policy are checked
Ongoing managementSeats, cost, support, audit and risk
People and structure changesLeavers, mergers and inherited permissions are handled explicitly
Export and closureData export, ending tasks, and revoking keys and permissions

Source

This page follows A13 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Identity, authorization and access decisions”; “Data and memory lifecycle”; “Regions, disaster recovery and exit”.

Was this page helpful?

MYRILUM platform architecture overviewSee how participants, the unified entry, business platform domains, the shared core, the agent layer, the execution network and infrastructure are layered, and how governance runs through all of them.Identity, authorization and access decisionsSign-in identity, task capability and approval for important actions are three different credentials; an action runs only when identity, action, authorization, data, budget and risk conditions all hold at once.Data and memory lifecycleMaterial is registered with its source, rights and purpose when it enters the platform; memory is kept apart by scope and is never a business ledger; reuse needs permission, and deletion is traceable to the end.Regions, disaster recovery and exitOne business contract, with data, keys, policies and runtime regions separated as needed; going global never means copying across borders by default. Reliability is not only staying up but also being able to recover, reconcile, explain and exit.What is available now?What MYRILUM officially operates today: distinguish website browsing, the member store, scoped delivery and component records, and check availability for the region and account.
Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
3ca63810e65600eb
Stable citation
MYRILUM-DOC-ARCH-013@0.1.0:en#overview

Machine-readableMarkdownMetadataJSON-LDChunks

This documentation grants no execution, release, or production authority.

Sources and maintenance

Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
3ca63810e65600eb
Stable citation
MYRILUM-DOC-ARCH-013@0.1.0:en#overview

This documentation grants no execution, release, or production authority.