User Attributes vs. User Profile Attributes

The Kinetic Platform supports two types of user-specific metadata: User Attributes and User Profile Attributes. While they serve similar purposes, they differ in how they are assigned, maintained, and used.

This guide explains the difference and how to configure both to support dynamic workflows, personalized experiences, and access control.

---

User Attributes

User Attributes are system-managed values that drive business logic, workflow behavior, form visibility, and access control.

Examples:

• Manager
• Department
• Region
• SupportLevel
• ClearanceLevel

Use Cases:

• Route approvals to a user's Manager
• Show a form only to users with ClearanceLevel = High
• Filter a dropdown based on Region

Who Manages Them:

Admins and system integrations (e.g., SSO mappings or API-based provisioning)

Note: These are not editable by the user through the UI.

How to Set:

1. Navigate to Configuration > Users
2. Select a user
3. Scroll to the Attributes section
4. Choose an existing attribute or add a new one

Attributes can either be defined in Definitions > Attributes or directly added from the dropdown.

---

User Profile Attributes

User Profile Attributes are editable fields tied to a user’s profile. These are ideal for user-specific preferences or data that users can manage themselves.

Examples:

• Phone Number
• Preferred Language
• Job Title
• Office Location

Use Cases:

• Pre-fill contact details on a form
• Display profile info on a portal page
• Drive localization or branding preferences

Who Manages Them:

Users (via UI or form), or admins (via Console or provisioning logic)

Profile attributes are typically exposed in portals or are editable via submissions.

How to Set:

1. Navigate to Configuration > Users
2. Select a user
3. Scroll to the Profile Attributes section
4. Edit directly or allow updates through form submissions

Profile attributes also require a defined Attribute Definition.

---

🔄 Summary Comparison

---

Best Practices

• Use User Attributes for any value that impacts automation or access
• Use Profile Attributes for anything the user might need to see or update themselves
• Keep naming consistent and avoid overlapping fields unless explicitly needed

---

Next Step

Continue by managing Team Membership or setting up Attribute Definitions.