Projects

A project is a kanban board of tasks. Every task in WebPinch belongs to exactly one project. Projects belong to either you (personal) or an organization (shared).

Personal vs organization projects

	Personal	Organization
Owned by	You	The org
Members	Just you	Anyone with an active org seat
Limits	2 projects on free, unlimited on Pro	1 project until the org has a paid seat — see Billing
Sidebar grouping	”Personal” section	Under each org’s name

You can move a project between scopes if you outgrow personal mode — though there’s no UI for that yet, you’d recreate it under the org.

Create a project

Dashboard → New Project.

Field	Required	Notes
Name	yes	Shown everywhere — keep it short
Website URL	no	Required if you want to run site audits. Also the default page in visual review.
Priority	no	Low / Medium / High. Default Medium. Pure metadata — doesn’t affect ordering.
Due date	no	Project-level deadline, separate from task due dates.
Color	no	One of: indigo, emerald, cyan, amber, violet, rose, slate. Used in sidebar and dashboard.
Organization	conditional	Only shown if you belong to one or more orgs. Pick which org owns the project, or leave blank for personal.

Default kanban columns

A new project ships with four columns:

Key	Label	Color
`backlog`	New Pins	gray
`in_progress`	In Progress	blue
`in_review`	In Review	yellow
`done`	Done	green

You can add, rename, reorder, recolor, or delete columns from Project Settings → Columns. The key is what the REST API and MCP server use as the status value when creating or updating tasks. The first column was called Backlog before it was renamed to New Pins — its key is still backlog, so existing API calls, filters and integrations keep working unchanged.

Don’t delete a column with tasks in it — the tasks become orphaned (still exist in the database, but invisible on the board). Move them out first.

Project settings

Project Settings (gear icon in the sidebar’s project menu) covers:

General — name, URL, priority, due date, color, star toggle
Members (org projects only) — see below
Columns — kanban board structure
Sharing — guest token + embed snippet for visual review and the browser extension
Authenticated proxy — for sites behind login (Google, GitHub, Azure AD, Auth0, Okta), so reviewers can pin issues without separate auth
Danger zone — delete the project (irreversible)

Members and roles

Org-project members carry one of three roles:

Role	Can
`owner`	Everything, including delete the project
`admin`	Edit settings, invite members, delete tasks
`member`	Create + edit tasks, post comments

Membership is inherited from the org by default — anyone with an active org seat can see all projects in that org. Direct project membership exists for cases where you want a contractor on one project but not the whole org. (See Billing for what counts as an “active org seat”.)

Stars and visibility

Click the star icon on a project card to pin it to a Starred section at the top of the dashboard. Useful for the 2–3 projects you’re actively working on out of dozens.

There’s no separate archive flag yet — to retire a project, set its column status manually, or delete it.

Project Settings → Integration exposes:

Guest token — the nanoid paired with the project. Anyone with this token can submit tasks via the extension or visual review URL. Treat it as semi-public — it grants write-only access to that project.
Embed snippet — a <script> tag you can drop into your own site’s footer to add the WebPinch widget for visitors.
Bookmarklet — drag-to-bookmark version of the widget that anyone can run on any page.

For programmatic access (read tasks, run audits, etc.), use a personal access token instead — guest tokens are write-only by design.