Create a project

Name, visibility, and defaults when starting a new project.

Projects are the boundary for permissions, notifications, and automation. Spending two minutes on naming and visibility up front prevents accidental exposure later—especially when customers or partners are invited.

Create flow

Click New project, choose a name, and pick visibility: workspace-only or invite-only. Invite-only is appropriate when content must not be discoverable by everyone in the org directory.

Naming

Use a name people will recognize in notifications and URLs. Avoid confidential codenames in titles if screenshots might leak; put codenames in an internal field instead.

Ownership

Assign an owner who can approve membership changes. Orphan projects without owners tend to accumulate stale access lists.

Templates

Start from blank or apply a template with prebuilt sections for your team’s process. Templates accelerate rollout but still need a quick review—remove sample text that could confuse readers.

Forking templates

When you customize a template heavily, save a new template version so other teams inherit your improvements instead of editing one-off copies.

Defaults

Set default labels and owners so new items do not land unassigned. Defaults reduce “triage debt” on Monday mornings when many items are created at once.

Iteration

Revisit defaults after major process changes (new severity model, new regions). Old defaults silently mis-route work if nobody updates them after a reorg.