Project Features

Not every project needs every tool. SetGet lets you enable or disable major features on a per-project basis so that the interface stays focused on what your team actually uses. Disabling a feature hides it from the sidebar, removes it from menus, and prevents members from creating new items of that type. Existing data is preserved and reappears if you re-enable the feature later.

Available feature toggles

Each project has the following features that can be independently toggled:

Feature	What it provides	Default
Cycles	Time-boxed iterations for planning and tracking sprints	Enabled
Modules	Cross-cutting groupings of work items by theme, initiative, or epic	Enabled
Views	Saved filters and custom perspectives on your work items	Enabled
Pages	Rich-text documents for specs, notes, meeting minutes, and wiki content	Enabled
Intake	A queue for incoming requests that can be triaged into work items	Disabled

How to toggle features

1. Open the project and go to Settings > Features.
2. You see a toggle switch for each feature.
3. Click a toggle to enable or disable the feature.
4. The change takes effect immediately.

No confirmation dialog is shown because disabling a feature does not delete any data — it only hides the feature from the interface.

TIP

Only project Admins can change feature toggles. If you do not see the Features section in settings, check your project role.

What each toggle controls

Cycles

When enabled:

• The Cycles section appears in the project sidebar.
• Members can create, edit, and manage time-boxed cycles.
• Work items can be added to cycles for sprint planning.
• Cycle analytics (burndown, velocity, scope change) are available.

When disabled:

• The Cycles section is hidden from the sidebar.
• The "Cycle" field disappears from work item details.
• Existing cycles and their associations are preserved but inaccessible.
• Cycle-related filters and grouping options are removed from views.

When to disable: Your team uses a continuous flow (Kanban) process and does not work in sprints.

Modules

When enabled:

• The Modules section appears in the project sidebar.
• Members can create modules to group related work items by theme, epic, or initiative.
• Module progress tracking (by state, priority, and estimate) is available.
• Work items can belong to one or more modules.

When disabled:

• The Modules section is hidden from the sidebar.
• The "Module" field disappears from work item details.
• Existing modules and associations are preserved but inaccessible.
• Module-related filters and grouping options are removed.

When to disable: Your project is small enough that labels and cycles provide sufficient organization, or your team does not use epic-level groupings.

Views

When enabled:

• The Views section appears in the project sidebar.
• Members can create and save custom filtered views of work items.
• Shared views are visible to all project members.
• Views support grouping, sorting, filtering, and layout preferences.

When disabled:

• The Views section is hidden from the sidebar.
• Saved views are preserved but inaccessible.
• Members can still use temporary filters in the work items list — they just cannot save them.

When to disable: Rarely. Views are lightweight and useful for almost every project. Consider disabling only if you want to minimize sidebar clutter for very small projects.

Pages

When enabled:

• The Pages section appears in the project sidebar.
• Members can create rich-text pages with a block-based editor.
• Pages support headings, lists, code blocks, embeds, tables, and more.
• Pages can be organized in a hierarchy and used as a team wiki.

When disabled:

• The Pages section is hidden from the sidebar.
• Existing pages are preserved but inaccessible.
• Links to pages from work item descriptions still exist but cannot be navigated.

When to disable: Your team uses an external wiki or documentation tool (e.g., Notion, Confluence) and does not want duplicate documentation surfaces.

Intake

When enabled:

• The Intake section appears in the project sidebar.
• External users or team members can submit requests through the intake queue.
• Admins and Members can triage incoming requests — accepting them as work items or declining them.
• Accepted requests are converted to work items with the project's default state.

When disabled:

• The Intake section is hidden from the sidebar.
• No new requests can be submitted.
• Existing intake items are preserved but inaccessible.

When to disable: Your project does not receive external requests, or you prefer to create all work items directly. Intake is disabled by default because most projects do not need it initially.

Effects of disabling a feature

Aspect	What happens
Sidebar	The feature section disappears
Work item fields	Related fields (Cycle, Module) are hidden
Filters and grouping	Feature-specific options are removed
Existing data	Preserved in the database, hidden from the UI
API	Feature endpoints still respond but return empty results
Re-enabling	All previous data reappears exactly as it was
Notifications	Feature-related notifications stop while disabled

WARNING

Disabling a feature does not delete data, but it does hide it from all members. Make sure your team is aware before toggling off a feature that is actively in use.

Recommended configurations by team style

Team style	Cycles	Modules	Views	Pages	Intake
Scrum team	On	On	On	On	Off
Kanban team	Off	On	On	On	On
Small project	Off	Off	On	On	Off
Client-facing project	On	On	On	On	On
Documentation project	Off	Off	On	On	Off
Open-source project	On	On	On	On	On

Best practices

• Start with defaults — enable everything at first, then disable features your team does not use after a few cycles.
• Communicate changes — let your team know before disabling a feature, especially if it has active data.
• Use Intake for external requests — if your project receives bug reports or feature requests from users outside your team, enable Intake instead of asking them to create work items directly.
• Keep Views enabled — Views are the most lightweight feature and provide significant value even for small teams.
• Re-evaluate periodically — as your project grows, features you initially disabled may become useful.

Related pages

• Manage Projects — Create and configure projects
• Project Settings — Full settings reference
• Planning with Cycles — Learn about sprint planning
• Planning with Modules — Organize work by theme or epic
• Views Overview — Create saved filters and perspectives
• Pages Overview — Write and organize documents
• Intake — Manage incoming requests