Project tags — Glueprint Docs

Once you have more than a few projects, telling them apart in the sidebar gets hard. Tags are a small visual cue — a name, a color, and a set of initials that follow a project everywhere it appears.

Tags are not limited on any plan. Create as many as you find useful.

Tag scopes

Every tag has a scope, chosen when you create it. The scope decides who can see it and who can use it.

Personal — only you. Good for side projects and local repositories that aren’t the whole organization’s business.
Team — everyone on one of your teams. Good for work owned by a single team.
Organization — everyone in the organization. This is the classic shared tag, and it is still the only scope that owners and admins manage on everyone’s behalf.

A tag’s scope is fixed once it is created. If you need a personal tag to become an organization tag, create the organization tag and re-tag the projects.

Who can create and manage tags

Any member can create personal tags and manage their own.
Any member of a team can create team tags for that team and manage them.
Owners and admins create and manage organization tags.
Owners and admins can manage every tag in the organization, including members’ personal tags. They see the tag’s name, owner, and how many projects use it — the same kind of existence metadata they already see for private hosts. It is not a way into the work behind the tag.

Names must be unique within their own scope, ignoring case. Your personal tag can share a name with an organization tag or with another member’s personal tag; you’ll only ever be told about a conflict inside your own scope, so tag names never leak between members.

Managing tags

Tags are managed in the portal under Settings > Project tags. The list is grouped by scope — your personal tags first, then a group per team, then the organization’s tags. Creating a tag asks for its visibility before its name.

Assigning tags to a project

Open a project and use the tag picker to assign a tag. The picker groups options the same way the settings list does.

Which tags a project can use depends on the host the project lives on:

A host shared with the whole organization can only use organization tags.
A host shared with one team can use that team’s tags and organization tags.
A private host can use anything its owner can see — organization tags, their teams’ tags, and their own personal tags.

This keeps a private tag off a machine that other people reach. If you try to assign a tag a host isn’t allowed to use, Glueprint refuses the assignment and tells you why.

If a host’s sharing setting changes later, projects can be left carrying a tag the host is no longer allowed to use. Glueprint doesn’t strip the tag; it flags the project and prompts you to re-tag it.

What other people see

A tag you can’t see simply isn’t there. Projects and sessions carrying it show up untagged — no placeholder, no hint that a tag exists. That is true across the sidebar, the dashboard, the project selector, and notifications.

Where tags show up

Sessions sidebar — tags appear as small chips next to a session’s project, so you can scan grouped work at a glance.
Dashboard — tags surface alongside project cards.
Portal header — the project selector dropdown lets you filter by tag.

What tags don’t do today

The file browser and editor breadcrumbs don’t show tags in the current release.
Clicking a tag chip directly doesn’t filter the sessions list; use the project selector or filter bar to scope by tag.
A tag’s scope can’t be changed after it is created.

Conventions

A few patterns that work:

One tag per team for work that belongs to a specific team.
A personal tag for the scratch and side projects you don’t want cluttering everyone’s view.
One tag per state (active, on hold, archived) if you juggle many in-flight projects.

Don’t over-tag. The point of tags is reducing visual clutter; using ten of them defeats the purpose.

Sessions > Search and filter for finding work across many projects.
Tasks and boards for the higher-level work tracking.