Flavors

Flavors in smenso are workspace-specific custom fields that extend the standard data model. They allow organizations to store additional metadata on projects, tasks, time records, users, status reports, and other objects.

What is a Flavor?

Flavors can be defined in different formats, for example:

• Text field
• Number field
• Date field
• Single-select
• Multi-select
• Boolean
• Formula

Flavors can be grouped and attached to different object types (e.g. projects, tasks, users).

Where Flavors Are Used

Flavors can appear on:

• Projects
• Tasks and subtasks
• Time records
• Status reports
• Users/members

They are visible in the UI, can be filtered and sorted in views, and are available in APIs and reports.

Workspace Scope

Flavors are configured per workspace and may differ between workspaces. Integrations should not assume that flavor definitions or identifiers are the same across environments.

Flavors in APIs

In APIs, flavors can usually be referenced by:

• GUID (flavor identifier, globally unique in the workspace), or
• Name (depending on the endpoint and implementation)

Flavors are:

• Included in responses (often in a flavors/tags/appliedTags structure)
• Writable via creation and update endpoints, where allowed
• Available in export/reporting APIs for analytics

Formula flavors are typically read-only and computed by the system.

Summary

Flavors extend smenso objects with workspace-specific custom fields. They support a range of field types, can be referenced by GUID or name (depending on the endpoint), and are available across XML, JSON, and Reporting APIs.