​
ORGANIZATION STRUCTURE & WORKSPACES

This diagram illustrates the clear hierarchy of functional units and business object types within the system. This format places the Function (the blueprint) directly under the Space (the instance) to clarify their relationship.
🏢 LAIKA (Organization)
│
├── 📂 MARKETING (Area)
│   └── ⏹️ Marketing Campaigns (Space)
│       └── 📋 Function: Marketing Campaigns
│           └── 🧊 Campaign
│               └── 🧊︎ Ad (Sub-Object)
│
├── 📂 SALES (Area)
│   └── ⏹️ Sales & CRM (Space)
│       └── 📋 Function: CRM
│           └── 🧊 Customer
│
├── 📂 ACCOUNTING (Area)
│   └── ⏹️ Contracts & Invoices (Space)
│       └── 📋 Function: Contract & Invoice
│           └── 🧊 Contract
│               └── 🧊︎ Invoice (Sub-Object)
│
├── 📂 DESIGN & CONSTRUCTION (Area)
│   ├── ⏹️ Project Management (Space)
│   │   └── 📋 Function: Project Management
│   │       └── 🧊 Project
│   │
│   ├── ⏹️ Design (Space)
│   │   └── 📋 Function: Interior Design
│   │       └── 🧊 Design Package
│   │           ├── 🧊︎ Functional Layout
│   │           ├── 🧊︎ Concept
│   │           ├── 🧊︎ 3D
│   │           ├── 🧊︎ 2D
│   │           └── 🧊︎ Revisions
│   │
│   └── ⏹️ Interior Construction (Space)
│       └── 📋 Function: Site Survey & Construction
│           ├── 🧊 Site Survey
│           │   └── 🧊︎ Constraint (Sub-Object)
│           └── 🧊 Construction
│
└── 📂 CUSTOMER SUCCESS (Area)
    └── ⏹️ Customer Success (Space)
        └── 📋 Function: Customer Success
            └── 🧊 Success Plan

​
USER MANAGEMENT

The system uses two types of accounts to clearly distinguish between human actions and automated system processes.
Account TypeDescriptionApplication at LAIKA
User AccountThe standard account for team members, associated with a specific person who logs into the platform to work and collaborate.For all LAIKA employees.
Functional AccountA special, non-login account used exclusively for Universal Automation to ensure a clear audit trail.A single account, automation@laika.com, will be created to execute all global automation rules.

​
OBJECT RELATIONSHIP MODEL

laika-er-global.png
A built-in, strict hierarchy between a standard Object and its Sub-Objects. This method is best for work breakdown structures.
Application at LAIKA:
Parent ObjectChild Object(s)Architectural Rationale
Marketing Campaigns/🧊CampaignMarketing Campaigns/🧊AdWork Breakdown Structure: Each Campaign is a major plan that contains multiple specific Ads.
Contract & Invoice/🧊ContractContract & Invoice/🧊InvoiceFinancial Breakdown Structure: A Contract’s total value is broken down into multiple Invoices corresponding to payment milestones.
Site Survey & Construction/🧊Site SurveySite Survey & Construction/🧊ConstraintWork Breakdown Structure: A Site Survey may identify and record multiple Constraints (issues to be addressed).
Interior Design/🧊Design PackageInterior Design/🧊Functional Layout, 🧊Concept, 🧊3D, 🧊2D, 🧊RevisionsWork Breakdown Structure: A master Design Package is broken down into sub-items for each phase of the design process.

​
WORKVIEWS, DASHBOARDS, FILTERS & REMINDERS

This section defines the tools for aggregating and presenting data from across all functions, helping users work efficiently and enabling leadership to make informed decisions based on a holistic view of the business.
These are pre-saved work screens at the global level, consolidating work items from various Spaces for operational management purposes.
Workview NameView TypeData Source & Filter LogicAudience
All Active ProjectsList ViewSource: Project Management/🧊Project
Logic: Status IS NOT “Completed” AND “Cancelled”		COO, Board of Directors, All Project Managers

​
GLOBAL LOGIC & AUTOMATION

Rules that connect Luklak with external applications and services (e.g., Website, Google, SEPAY, Email).
Rule #Rule NameBusiness Description
CF-01Receive Lead from Landing PageWhen a form is submitted on the website, a Webhook triggers the creation of a CRM/🧊Customer and links it to the source Marketing Campaigns/🧊Ad.
CF-02Create Google Calendar EventA Sales user clicks a button on a CRM/🧊Customer, sending an HTTP Request via N8N to create an event in Google Calendar.
CF-05Create Google Docs ContractAn Accountant clicks a button, sending an HTTP Request via N8N to populate a Google Docs template with contract data.
CF-06Log Payment from SEPAYSEPAY sends a Webhook upon payment, which finds the corresponding Contract & Invoice/🧊Invoice and updates its status.
CF-10Send Concept Email to CustomerA Sales user clicks a button to automatically compose and send a personalized Email with design details to the customer.

​
ACCESS & GOVERNANCE

This is the highest level of permissions, acting as the “entry ticket” to the entire system and defining a user’s maximum potential authority.
Privilege LevelAssigned to (at LAIKA)Permission Description
OwnerCEOThe highest level. Manages billing, can transfer ownership, and holds all Admin privileges.
AdminCOO, System AdministratorCan configure everything in the system, from Global Settings to user management.
App ManagerHeads of Areas (e.g., Head of Sales, Head of Design…)A specialized role that can design, edit, and manage Functions 📋.
MemberAll remaining employeesThe standard privilege for most users, allowing them to work within the Spaces ⏹️ they are given access to.