Skip to main content

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.
  • Unified Organization Structure
  • Workspace List
This diagram illustrates how the HR-related functions are logically organized within a dedicated Area, enabling centralized management and security.
🏢 ACME Corporation (Organization)

└── 📂 Human Resources (Area)
    ├── ⏹️ Employee Records (Space)
    │   └── 📋 Function: HR Information System
    │       └── 🧊 Employee

    ├── ⏹️ Recruitment (Space)
    │   └── 📋 Function: Recruitment Management
    │       └── 🧊 Candidate

    ├── ⏹️ Onboarding & Offboarding (Space)
    │   └── 📋 Function: Employee Onboarding/Offboarding
    │       ├── 🧊 Onboarding
    │       └── 🧊 Offboarding

    └── ⏹️ HR Requests (Space)
        └── 📋 Function: HR Request
            └── 🧊 Request

USER MANAGEMENT

  • Account Management
  • Global Groups
  • Global Roles
The system will utilize two types of accounts to distinguish between actions taken by employees and those performed by automated processes.
Account TypeDescriptionApplication at ACME Corp
User AccountA standard account for team members who log in to the platform to perform their work and collaborate.For all ACME Corporation employees.
Functional AccountA special, non-login account used exclusively by the automation engine to execute rules, ensuring a clear audit trail and consistent permissions.A single account, hr.automation@acme.com, will be created to execute all cross-functional HRM automation rules.

OBJECT RELATIONSHIP MODEL

  • Parent-Child Relationships
  • Global Connections
  • Object Picker Fields
  • Data Table Fields
This creates a strict, hierarchical link where a “child” object is a component of a “parent” object. It is ideal for breaking down a large piece of work into smaller, manageable tasks.
Application at ACME Corp:
Parent ObjectChild Object(s)Architectural Rationale
🧊 Onboarding Process🧊︎ Onboarding TaskWork Breakdown: An 🧊 Onboarding Process is a complex procedure. Breaking it down into individual 🧊︎ Onboarding Tasks (e.g., “Prepare Laptop,” “Set up Payroll”) allows for clear assignment and tracking of sub-items.
🧊 Offboarding Process🧊︎ Offboarding TaskWork Breakdown: Similar to onboarding, the offboarding process is broken down into distinct tasks (e.g., “Return Assets,” “Revoke System Access”) for accountability.

WORKVIEWS, DASHBOARDS, FILTERS & REMINDERS

This section defines the cross-functional reporting and data aggregation tools. These components will provide HR staff, managers, and leadership with the necessary insights to make informed decisions.
  • Global Workviews
  • Global Dashboards
  • Global Saved Filters
  • Filter Reminders
Workviews are pre-configured screens for day-to-day operational management, consolidating work items from various sources.
Workview NameView TypeData Source & Filter LogicAudience
All Open HR RequestsList ViewSource: HR Request/🧊Request
Logic: Status IS NOT “Completed” AND “Rejected”
HR Department

GLOBAL LOGIC & AUTOMATION

This section details the automation rules that connect the HRM functions, now ordered chronologically to represent the entire employee journey.
  • Cross-System Automation
  • Cross-Function Automation
These rules connect Luklak with external applications and your company website.
SequenceRule #Rule NameBusiness Rationale
1CS-01Post Job Opening to WebsiteA user clicks a button on a job opening record in the Recruitment space, which sends a Webhook to your company’s website CMS to automatically publish the job listing on the careers page.
2CS-02Receive Candidate ApplicationWhen a candidate applies via the company website or a connected job board (e.g., LinkedIn), a Webhook sends the application data to Luklak, automatically creating a new Recruitment/🧊Candidate object with the status “New,” including their attached CV.

ACCESS & GOVERNANCE

  • Tier 1: Business Privilege
  • Tier 2: Item Access
  • Tier 3: Permission & Notification Schemes
This is the highest level of permission, defining a user’s maximum potential authority within the system.
Privilege LevelAssigned To (at ACME Corp)Permission Description
OwnerCEOHas complete control over the entire organization, including billing and ownership transfer.
AdminHead of HR, System AdministratorCan configure all system-wide settings, manage users, and access all data.
App ManagerSenior HR Process SpecialistCan design, edit, and manage the four core HRM Functions (the blueprints).
MemberAll other employeesThe standard privilege for users to work within the Spaces they are granted access to.