Attribute Definitions

Attributes let you store custom configuration values and metadata across the platform—without needing to hard-code logic. You can use them to influence workflows, display logic, access permissions, and user experience.

---

What Are Attributes?

Think of attributes as tags, variables, or settings that can be attached to:

• Spaces
• Kapps
• Forms
• Categories
• Teams
• Users
• Datastore Forms

Once defined, they become reusable building blocks across workflows, portals, and security rules.

---

Defining Attributes

Before setting an attribute on a resource, you must define it.

Each Attribute Definition includes:

• Name – Reference key (used in expressions or APIs)
• Description – Explains the attribute’s purpose
• Allows Multiple – If true, this attribute can hold multiple values (e.g., tags or keywords)

You can define attributes in the Definitions > Attributes area of the Console.

---

Types of Attributes

Each resource has its own attribute types and usage patterns:

User Profile Attributes can be edited by the user. Regular User Attributes can only be edited by someone with user modification privileges.

---

How Attribute Resolution Works

Attributes are hierarchical. The platform checks for values from the most specific to the most general:

1. Form
2. Kapp
3. Space

If the same attribute name exists at multiple levels, the most specific one takes precedence.

---

Common Use Cases

• Portal Theming
  Set headerColor as a Space attribute to control branding without editing CSS

• Workflow Routing
  Use a Team attribute like Manager to dynamically assign approvals

• Form Behavior
  Display or hide fields based on Form-level or User-level attributes

• Security Policies
  Reference attributes in JavaScript expressions to control access

---

Related Topics

• Security Definitions to learn how access rules can use attributes to dynamically grant or restrict visibility.