Functions governance

User roles and Functions permissions

With the custom user roles feature, you can customize user permissions related to Functions, including the following selections:

• Create, edit, and archive or View only
• Test: Can test functions in the editor

When to centralize function creation

Centralize when:

• Functions enforce compliance or validation rules
• Functions create or update records in critical tables (master data, audit logs) or shared tables
• Embedding Connector Functions
• Your organization has many citizen developers with varying skill levels

Centralized model:

• Function creators: Tulip champion, IT/OT team, solution architects
• Function users: All app builders
• Approval process: Function changes require review
• Documentation: Central repository of function specifications

When to decentralize function creation

Decentralize when:

• Apps are isolated (don't share tables or logic)
• Small team of experienced app builders
• Rapid iteration is more important than strict governance
• Functions are app-specific, not reusable

Decentralized model:

• Function creators: Any app builder
• Function users: Same app builder or their immediate team
• Approval process: Lightweight or none
• Documentation: Optional, embedded in function names

Training path for new app builders

First: Learn to use functions

• Understand what functions are and why they exist
• Call pre-built functions from triggers
• Map inputs and outputs correctly

Then: Learn to modify functions

• Update function logic (non-breaking changes)
• Test functions
• Understand where-used implications

Finally: Learn to create functions

• Identify opportunities for new functions
• Design input/output signatures
• Implement complex logic
• Document functions for others

Rationale: Most app builders primarily use functions created by others. Focus training on usage first, creation later.

Additional Resources