Core Concepts
SetGet is built around a set of interconnected concepts. Understanding how they relate to each other helps you get the most out of the platform. This page covers every major building block, from the highest-level container down to individual properties.
Workspace
A workspace is the top-level organizational unit in SetGet. Think of it as your company or team's home base — everything else lives inside it.
A workspace contains:
- Projects — where actual work is tracked
- Members — the people who have access
- Teamspaces — optional groupings of members across projects
- Chat channels — real-time messaging
- Dashboards — custom data visualizations
- Analytics — workspace-wide reporting
- Settings — billing, authentication, integrations, and more
Most organizations have a single workspace. Larger enterprises may use multiple workspaces to separate divisions or business units.
Learn more: Manage Workspaces
Project
A project is a container for related work within a workspace. Each project has its own:
- Work items — the tasks and issues to track
- States — the workflow stages (e.g., Todo → In Progress → Done)
- Labels — categorization tags (e.g., Bug, Feature, Improvement)
- Estimates — effort estimation system (points, time, or categories)
- Members — who can access and contribute to the project
- Cycles — time-boxed sprints
- Modules — feature-based groupings
- Views — saved filter configurations
- Pages — documentation and wiki
Projects are identified by a short code (e.g., WEB, API, MOBILE). This code becomes the prefix for every work item ID in the project — WEB-1, WEB-2, and so on.
Learn more: Manage Projects
Work item
A work item is the fundamental unit of work in SetGet. It represents anything your team needs to do — a feature to build, a bug to fix, a task to complete, or an improvement to make.
Every work item has these core properties:
| Property | Description |
|---|---|
| Title | A short, descriptive name for the work |
| Description | Detailed context, requirements, or reproduction steps |
| State | Current position in the workflow (e.g., In Progress) |
| Priority | Urgency level: Urgent, High, Medium, Low, or None |
| Assignees | One or more team members responsible for the work |
| Labels | Tags for categorization (e.g., Bug, Frontend, P1) |
| Estimate | Effort estimate (points, hours, or categories) |
| Due date | When the work should be completed |
| Start date | When work is expected to begin |
| Parent | A parent work item (for hierarchical relationships) |
| Cycle | The sprint this work belongs to |
| Module | The feature group this work belongs to |
Work items also support attachments, comments, activity history, relations (blocking, blocked by, related, duplicate), and subscriptions for notifications.
Learn more: Manage Work Items
State
A state represents a stage in your workflow. SetGet organizes states into five groups that reflect the lifecycle of any work item:
| Group | Meaning | Color |
|---|---|---|
| Backlog | Acknowledged but not yet planned | Gray |
| Unstarted | Planned but not yet started | Blue |
| Started | Actively being worked on | Orange/Yellow |
| Completed | Successfully finished | Green |
| Cancelled | Will not be done | Red |
You can create as many custom states as you need within each group. For example, "Started" might contain "In Development", "In Review", and "QA Testing".
The order of states within each group defines the workflow progression visible in Kanban columns and Gantt charts.
Learn more: Workflow States
Cycle
A cycle is a time-boxed iteration — the SetGet equivalent of a sprint. Cycles help your team commit to delivering a specific set of work items within a defined period (typically 1–4 weeks).
Key cycle features:
- Start and end dates define the iteration window
- Work items are added from the backlog or created directly in the cycle
- Progress tracking shows completed vs. remaining work in real time
- Burndown analytics help you understand team velocity
- Transfer — uncompleted work items can be moved to the next cycle
- Archive — completed cycles are archived for historical reference
Cycles exist at the project level. Each project can have one active cycle and multiple upcoming or completed cycles.
Learn more: Cycles
Module
A module is a thematic grouping of work items — typically representing a feature, epic, or area of the product. Unlike cycles (which are time-based), modules are scope-based.
For example:
- "User Authentication" module might contain sign-up, login, password reset, and SSO work items
- "Dashboard Redesign" module might span across multiple cycles
Modules have their own status (Backlog, Planned, In Progress, Completed, Cancelled), lead and member assignments, start/end dates, and link collections.
A single work item can belong to both a cycle and a module simultaneously, giving you two complementary perspectives on progress.
Learn more: Modules
View
A view is a saved combination of filters, layout, grouping, and ordering settings. Views let you create reusable perspectives on your work without changing the underlying data.
SetGet supports two levels of views:
- Project views — scoped to a single project
- Workspace views — span across all projects (e.g., "All my assigned items")
Each view can use any of the five layouts (List, Kanban, Spreadsheet, Calendar, Gantt) and any combination of filters.
Learn more: Views
Page
A page is a rich-text document within a project. Pages serve as your team's knowledge base — meeting notes, technical specs, process docs, wikis, and more.
The page editor supports:
- Headings, paragraphs, and lists
- Tables and code blocks with syntax highlighting
- Images, embedded diagrams (Draw.io), and file attachments
- Slash commands for quick block insertion
- AI-powered writing assistance
- Inline comments for collaborative feedback
- Version history for tracking changes
Pages can be nested to create hierarchical documentation structures, and they can be published publicly for external stakeholders.
Learn more: Manage Pages
Label
A label is a color-coded tag applied to work items for categorization. Labels are defined at the project level and can represent anything meaningful to your team — bug types, priority tiers, components, teams, or effort sizes.
Labels support parent-child hierarchy, so you can group related labels (e.g., "Platform" → "iOS", "Android", "Web").
Learn more: Work Item Labels
Estimate
An estimate represents the expected effort for a work item. SetGet supports three estimation systems:
- Points — numeric values (Fibonacci, linear, or custom)
- Categories — text-based sizes (XS, S, M, L, XL)
- Time — hour-based estimates
Estimates are configured at the project level. When enabled, you can assign an estimate to each work item and track total estimated effort in cycles and modules.
Learn more: Project Estimates
Teamspace
A teamspace is an organizational layer that groups workspace members into cross-project teams. Teamspaces let you see all work, cycles, views, and pages relevant to a specific team — even if that work spans multiple projects.
Teamspaces are optional and most useful for organizations with many projects and overlapping team membership.
Learn more: Teamspaces
Inbox and notifications
SetGet's notification center (inbox) collects all activity relevant to you — assignments, mentions, comments, status changes, and more. You can mark notifications as read, snooze them, or archive them.
Notification preferences let you control which events trigger alerts and whether you receive them in-app, via email, or both.
Learn more: Notification Center
Dashboard
A dashboard is a customizable view of workspace metrics. You can add widgets to display charts, tables, and summaries — cycle burndowns, work item distributions, team workload, and more.
Dashboards are workspace-level, so they can aggregate data across all projects.
Learn more: Dashboards
How concepts connect
Here is how all the concepts fit together:
Workspace
│
├── Members (roles: Admin, Member, Guest)
├── Teamspaces (cross-project team groupings)
├── Chat Channels (real-time messaging)
├── Dashboards (workspace-wide metrics)
├── Analytics (reporting and insights)
│
└── Projects
├── Work Items
│ ├── Properties (state, priority, assignees, labels, dates, estimates)
│ ├── Relations (parent/child, blocking, related, duplicate)
│ ├── Comments and Activity
│ └── Attachments
├── States (workflow stages within 5 groups)
├── Labels (categorization tags)
├── Estimates (effort system configuration)
├── Cycles (time-boxed sprints)
├── Modules (feature-based groupings)
├── Views (saved filter perspectives)
└── Pages (documentation and wiki)Related pages
- Introduction — What SetGet is and why teams use it
- Quickstart Guide — Set up your first project in 5 minutes
- Tutorials — Hands-on walkthroughs for every feature
- Glossary — Definitions of all SetGet terminology