Create Context Type

Create a new Context Type that defines states, metadata, description, allowed activities, sub-contexts, and scheduling. You’ll do this from Templates → Context Types → New Context Type in the dashboard.

Steps

Open the Context Type Editor**

• In the sidebar, go to Templates.
• Select Context Types.
• Click New Context Type (top-right).

Settings

• Fill Context Type Name (singular) and Context Type Name (plural) — used across the system.
• Add a Context Type Description (for dashboard search and context info; dashboard-only).
• Visibility & placement options:
  • Primary Context — mark as a primary context type.
  • Show in custom menu — adds the context to the dashboard side menu (hover over the context folder icon).
  • In App — make the context visible in the mobile app.
  • Hide Context Type if no accessible sub-elements for the user — if the user has no accessible activities within this context, the context won’t appear in the app at all.
• Template Owner — defaults to the creator; can be changed.
• Lock Template — adds a guard to prevent accidental edits (must be unlocked to change later).
• Context Type Code Editor — for Zegeba/administrators only. Advanced use; incorrect edits can break the template.

States

• Define lifecycle states for the context.
• For each state, set:
  • State Name (required)
  • Progress value in % (numeric)
  • State Color (required)
  • Help Text (shown in dashboard)
  • Default — mark the state used when creating new contexts
  • Hide Context with this state — hide the context while this state is active
• Use + New state at the bottom to add states.
• Use the action menu (⋮) to Move Up, Move Down, or Delete a state.

Meta Data

• Create fields that store metadata for the context.
• For each field, set:
  • Display Name*, Element ID, Type, Help Text
  • Required and Lock After First Save (for values captured only at creation)
  • Default value (where supported)
  • Autofill value from levels above — provide the Element ID of the source field to inherit from parent levels.
• Available Types include: Text, Text Area ( New), Dropdown list, Date, Date Time, List of users, List of user emails, Dynamic List.

Description

• Configure default Context Title, Context Description, and Help Text (shown in the app via the ? icon).
• You can use parameters to pull values from metadata fields into the title/description.

Activities

• Choose which Activity Templates can be used within this context:
  • All, Selection, or None.
• If Selection is chosen:
  • Add entries in the left column (e.g., Settings, Untitled…), and pick the specific activity template for each.
• Optional: allow users to add existing activities into this context.

Contexts

• Define which Context Types may be used as Sub-contexts:
  • All, Selection, or None.
• If Selection is chosen, add and configure items in the left column.

Scheduling

• Configure due-date behavior and visibility controls:
  • Due date (enable/disable), Time format (UTC or Local Time), Display as (Time remaining or Date & Time).
  • Visibility windows with UTC/Local time options.

Save

• Click Save (top-right). Use Lock Template if you want to prevent accidental edits.

FAQs

What’s the difference between “Show in custom menu” and “In App”?

• Show in custom menu adds the context type to the dashboard side menu. In App controls whether the context type is visible on mobile App.

Can I reorder states later?

• Yes. Use the state’s action menu (⋮) → Move Up/Down.

What happens if I lock a metadata field after first save?

• With Lock After First Save enabled, the field becomes read-only for that context after it’s been saved once.

If I enable “Hide Context with this state,” where is it hidden?

• The context is hidden in the app while the selected state is active; it remains manageable in the dashboard.

Can I restrict which Activity Templates are used?

• Yes. Choose Selection and pick only the templates you allow in this context type.

How do Dynamic Lists work in Meta Data?

• They populate choices from a data source defined by your Zegeba configuration.

Who can use the Context Type Code Editor?

• Zegeba staff and administrators only. Use with caution; incorrect edits can break the template.

Article ID: 289