Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Quick Start Guide

Create an Organization and Project, then set navigation defaults for daily work.

Overview

Use this guide after sign-in is working. The outcome is a working Organization and Project.

What is covered

  • Create an Organization

  • Create a Project

  • Learn the core navigation patterns

  • Create a baseline Save View for repeatable reviews

At a glance

  • Time: ~15–30 minutes

  • Access: Account Admin for Organization creation + Project creation permission

Screenshot placeholder: account navigation with Organizations highlighted.

Key Concepts

  • Organization: container for a client, department, or business unit

  • Project: delivery container inside an Organization

  • Save View: stored view configuration for repeatable lists

How It’s Used

Use this guide during initial rollout. Use it for repeatable onboarding of additional Organizations.

Benefits

  • Faster setup for the first Project

  • Cleaner navigation and fewer “lost in scope” issues

Setup Steps

Prerequisites

  • Sign-in is working.

  • An Organization name is available (client, department, or business unit).

  • A Project name is available.

If Organization or Project creation is not available, request access from an admin.

Follow the steps in order.

1

Create an organization

Organizations separate work by client, department, or business unit.

Screenshot placeholder: Organizations list with New organization highlighted.

2

Create a Project

Create a Project inside the new Organization.

Screenshot placeholder: organization header with New project (or Add project) action highlighted.

3

Learn the interface basics

Get oriented on navigation, scope, and search.

GIF placeholder: switch organization → project and point out breadcrumbs + global search.

4

Create a baseline Save View

Save Views reduce rework during weekly reviews.

  1. Navigate to Tasks or Requirements in the Project.

  2. Apply a minimal filter set, such as Status != Complete.

  3. Select Save view (or equivalent action).

  4. Name the view with intent, such as Team — Weekly review.

GIF placeholder: create a filtered list, then save it as a team view.

Best Practices

  • Create a small first Project and iterate.

  • Establish a naming pattern before creating many Projects.

  • Confirm access scope before inviting external stakeholders.

Summary

Common next workflows:

Support routing:

Last updated