Guides
Start typing to search…

Accounts, Organisations & Addresses

In DJUST, entity management is based on a clear hierarchy that structures how platform actors interact.

Three core concepts define this structure: Account, Organisation, and Address.

  • The Account is the main entity grouping and managing multiple Organisations.
  • An Organisation represents a subdivision within the Account.
  • An Address is a key element associated with both users and organisations. It can be used for billing, shipping, or other logistics purposes.

This structure provides flexibility and efficiency in managing commercial and logistical operations, enabling customization to meet each business’s specific needs on the DJUST platform.


%%{init: {
  "theme": "base",
  "themeVariables": {
    "primaryColor": "#0080ff",
    "primaryTextColor": "#ffffff",
    "secondaryColor": "#ffffff",
    "secondaryTextColor": "#1A2A44",
    "tertiaryColor": "#FFAF40",
    "tertiaryTextColor": "#1A2A44",
    "lineColor": "#1A2A44",
    "fontFamily": "Poppins, sans-serif"
  }
}}%%

graph TD
    Compte["Account_"]
    Compte --> Org1["Org 1_"]
    Org1 --> SubOrg1["Sub-Org 1__"]
    Org1 --> SubOrg2["Sub-Org 2__"]
    SubOrg1 --> Utilisateur4["👤 User 4__"]
    SubOrg1 --> Adresse4["Addr 4_"]
    SubOrg2 --> Utilisateur5["👤 User 5__"]
    SubOrg2 --> Adresse4

    Compte --> Org2["Org 2_"]
    Org2 --> Utilisateur1["👤 User 1__"]
    Org2 --> Utilisateur2["👤 User 2__"]
    Org2 --> Adresse1["Addr 1_"]
    Org2 --> Adresse2["Addr 2_"]

    %% Styling
    classDef compte fill:#0080ff,stroke:none,color:#ffffff,font-size:12px,border-radius:12px
    classDef org fill:#3a37c2,stroke:none,color#ffffff,font-size:11px,border-radius:12px
    classDef suborg fill:#49CDFB,stroke:none,color:#ffffff,font-size:11px,border-radius:12px
    classDef user fill:#fff,stroke:#1A2A44,color:#1A2A44,font-size:10px,border-radius:8px
    classDef adresse fill:#FFAF40,stroke:none,color:#1A2A44,font-size:10px,border-radius:50%

    class Compte compte
    class Org1,Org2 org
    class SubOrg1,SubOrg2 suborg
    class Utilisateur1,Utilisateur2,Utilisateur4,Utilisateur5 user
    class Adresse1,Adresse2,Adresse4 adresse

    %% Line style
    linkStyle default stroke:#1A2A44,stroke-width:1.5px

Account

An Account represents a commercial entity (e.g., a company or B2B client) using the DJUST platform to purchase products.

Key Characteristics

  • It can be created in two ways:

    • By the customer themselves, if the front office is publicly accessible.
    • From the back office by an operator if the account already exists in an external system.

  • An account can be used across multiple stores.

  • Accounts cannot be empty — upon creation, you must create and attach at least one client user and one address.

  • Several objects can be linked to a single account:

    • Customer users (FOC Users)
    • Addresses
    • Organisations

  • Account structures can be enriched with custom fields (e.g., account type: premium vs. basic).

Organisation

An Organisation is part of an account and can itself contain multiple sub-organisations.

Key Characteristics

  • It can be created in two ways:
    • By the customer themselves from their My Account section (if this option is enabled in the front).
    • From the back office by an operator if the organisation already exists in an external system.
  • An organisation does not need to be linked to a user at creation time.
  • An organisation can also be used across multiple stores.
  • Several objects can be linked to an organisation:
    • Customer users (FOC Users)
    • Addresses
    • Sub-organisations
  • Organisation structures can be enriched with custom fields (e.g., external organisation codes).

Addresses

An Address on the DJUST platform represents a location record associated with either a user or an organisation.

Key Characteristics

  • It can be created in two ways:
    • By the customer themselves from their My Account section (if this option is enabled in the front).
    • From the back office by an operator if the address is already known.
  • An address can be used across multiple stores.
  • An address can be assigned one or more roles:
    • Billing
    • Shipping
  • Client users do not have address fields of their own — they inherit addresses from their organisation or account.

%%{init: {
  "theme": "base",
  "themeVariables": {
    "primaryColor": "#0080ff",
    "primaryTextColor": "#ffffff",
    "secondaryColor": "#ffffff",
    "secondaryTextColor": "#1A2A44",
    "tertiaryColor": "#FFAF40",
    "tertiaryTextColor": "#1A2A44",
    "lineColor": "#1A2A44",
    "fontFamily": "Poppins, sans-serif"
  }
}}%%

graph TD
    Account["🏢 Account__"]
    Account --> Addr1["Acc address__"]
    Account --> OrgA["Org A_"]
    Account --> OrgB["Org B_"]
    OrgA --> User1["👤 User A1__"]
    OrgA --> User2["👤 User A2__"]
    OrgB --> User3["👤 User B1__"]
    OrgA --> Addr2["Org address___"]    
    OrgB --> Addr3["Org address___"]        
    User1 --> Addr1
    User1 --> Addr2
    User2 --> Addr1
    User2 --> Addr2
    User3 --> Addr1
    User3 --> Addr3
    

    %% Styling
    classDef account fill:#0080ff,stroke:none,color:#ffffff,font-size:12px,border-radius:12px
    classDef org fill:#3a37c2,stroke:none,color#ffffff,font-size:11px,border-radius:12px
    classDef user fill:#F7F9FC,stroke:#1A2A44,color:#1A2A44,font-size:10px,border-radius:10px
    classDef address fill:#FFAF40,stroke:none,color:#1A2A44,font-size:10px,border-radius:50%

    class Account account
    class OrgA,OrgB org
    class User1,User2,User3 user
    class Addr1,Addr2,Addr3 address

    linkStyle default stroke:#1A2A44,stroke-width:1.5px

Updated about 2 months ago