ORGANIZATION STRUCTURE & WORKSPACES
This is a Scalable Example: The structure shown here is for demonstration purposes. You can add, remove, or rename any
📂 Area
, ⏹️ Space
, 📋 Function
, or 🧊 Object
to perfectly tailor the system to your company’s unique workflow.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.
USER MANAGEMENT
The system uses two types of accounts to clearly distinguish between human actions and automated system processes.
Account Type | Description | Application at LAIKA |
---|---|---|
User Account | The standard account for team members, associated with a specific person who logs into the platform to work and collaborate. | For all LAIKA employees. |
Functional Account | A 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

A built-in, strict hierarchy between a standard
Object
and its Sub-Objects
. This method is best for work breakdown structures.Parent Object | Child Object(s) | Architectural Rationale |
---|---|---|
Marketing Campaigns/🧊Campaign | Marketing Campaigns/🧊Ad | Work Breakdown Structure: Each Campaign is a major plan that contains multiple specific Ads . |
Contract & Invoice/🧊Contract | Contract & Invoice/🧊Invoice | Financial Breakdown Structure: A Contract ’s total value is broken down into multiple Invoices corresponding to payment milestones. |
Site Survey & Construction/🧊Site Survey | Site Survey & Construction/🧊Constraint | Work Breakdown Structure: A Site Survey may identify and record multiple Constraints (issues to be addressed). |
Interior Design/🧊Design Package | Interior Design/🧊Functional Layout , 🧊Concept , 🧊3D , 🧊2D , 🧊Revisions | Work 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 Name | View Type | Data Source & Filter Logic | Audience |
---|---|---|---|
All Active Projects | List View | Source: 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).
You can open this canvas view for better readability

Rule # | Rule Name | Business Description |
---|---|---|
CS-01 | Receive Lead from Website | When a form is submitted on the website, a Webhook triggers the creation of a Sales & CRM/🧊Customer and links it to the source Marketing/🧊Ad . |
CS-02 | Create Google Calendar Event | A Sales user clicks a button on a Sales & CRM/🧊Customer , sending an HTTP Request via N8N to create an event in Google Calendar. |
CS-04 | Create Google Docs Contract | An Accountant clicks a button on a Contract & Invoice/🧊Contract , sending an HTTP Request to populate a Google Docs template with Object data. |
CS-05 | Log External Payment | An external payment gateway sends a Webhook upon payment, which finds the corresponding Contract & Invoice/🧊Invoice and updates its status. |
CS-08 | Send Concept Email to Customer | A Sales user clicks a button to automatically compose and send a personalized Email with design variables and links 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 Level | Assigned to (at LAIKA) | Permission Description |
---|---|---|
Owner | CEO | The highest level. Manages billing, can transfer ownership, and holds all Admin privileges. |
Admin | COO, System Administrator | Can configure everything in the system, from Global Settings to user management. |
App Manager | Heads of Areas (e.g., Head of Sales, Head of Design…) | A specialized role that can design, edit, and manage Functions 📋. |
Member | All remaining employees | The standard privilege for most users, allowing them to work within the Spaces ⏹️ they are given access to. |