​
Why This Matters

Building custom business applications is traditionally a trade-off. You can either spend months and significant budget on custom code, or you can buy rigid, off-the-shelf software that forces your team into pre-defined workflows. Neither solution is ideal for a fast-moving, unique business.
The 📋 Function is Luklak’s answer to this dilemma. It is a powerful, no-code design paradigm that allows you, the architect, to design, package, and deploy a complete business solution without writing a single line of code. A Function bridges the gap between inflexible apps and complex development, empowering you to build the exact operational tools your business needs, precisely when you need them.

​
The Big Picture: The Blueprint and the Building

The easiest way to understand the relationship between a 📋 Function and a ⏹️ Space is through the analogy of an architectural blueprint and a physical building.
  1. The Blueprint: 📋 Function A Function is the master design plan. It is a container that packages all the necessary Tier 1 “LEGO pieces” for a specific business operation.
  2. The Building: ⏹️ Space A Space is the live, operational workspace created from the Function blueprint. This is where your team actually works with live data.
Think of it this way: A Function is the architect’s blueprint, and a Space is the actual building constructed from that plan. You can build many different houses from one single blueprint.

​
Anatomy of a Function

When you are in the design canvas of a 📋 Function, you are assembling these core components into a cohesive whole:

Object Types

The core data models of your process (e.g., Leads, Deals).

Workflows & Data Fields

The heart of the logic, defining how Objects move and what info they contain.

Workviews & Dashboards

The UI layers for interacting with and analyzing live data in a Space.

Automations

The process brain that eliminates manual work and connects steps automatically.

Roles

Define the actors in your process (e.g., Manager, Member, Approver).

Permission Schemes

The security matrix defining exactly who can do what for each Role.

Notification Schemes

The awareness layer defining who gets notified about which events.

​
Function Access Control (Item Access)

Beyond the components inside a Function, it’s critical to control who can interact with the Function blueprint itself. This is managed through a separate, system-level permission layer. This “Item Access” control determines which users or teams can:
  • View the Function in the library.
  • Use the Function to create new ⏹️ Spaces.
  • Edit or Manage the Function’s design.
Function Access Control is a global setting managed by system administrators. It ensures that only authorized architects can modify or deploy specific business blueprints, maintaining architectural integrity across the organization.
For a complete guide on this topic, please see the global settings documentation.

​
What’s Next?

Understanding the Function concept is the key to unlocking true architectural power in Luklak. Now that you’ve grasped the theory, the next step is to put it into practice.