Address book.

A per-workspace contact list of people you frequently invite to projects as stakeholders — partner PMs, regulators, security auditors, customer leads. The address book is a typing shortcut, not an access-control surface.

Reach it from Team → Address book in the top nav.

What's in a contact #

Each row stores six fields:

• Name — full name.
• Email — the address that gets the portal link when you invite them.
• Title — role at their organization (display only).
• Organization — their employer / team name.
• Department — picks one of the workspace's department tags so wish forms pre-fill correctly when they file from a portal.
• Favorite — flagged with a ★. Favourites sort first in the picker on the project Share panel.

None of this grants access. Adding someone to the address book does not give them a SpecGraph login, does not invite them to a project, and does not email them. It just remembers their details so the next invite is one click instead of four typed fields.

How it speeds up invites #

When the address book has at least one contact, the project's Share panel grows a Pick from address book combo above the manual fields. Selecting a name fills:

• email
• name
• organization
• department

…in one click. Edit any field and the picked-contact link drops automatically — your edits aren't pretending to come from the saved row.

If you haven't added anyone yet, the Share panel shows a tip pointing here.

Managing contacts #

The page lists every contact in the workspace, with a search field that matches name, email, organization, or title. Owners and admins can:

• Add a contact — opens a dialog with the six fields.
• Edit a contact — pencil action on the row; opens the same dialog pre-filled.
• Toggle favourite — star icon on the row.
• Remove a contact — trash icon, with a confirm dialog.

Editors and viewers see the list and can pick from it during invites, but cannot add, edit, or remove contacts.

When to add someone here #

Good candidates:

• A regulator you'll send 5+ specs to over the next year.
• A partner PM who reviews every release brief.
• A security auditor who signs off on the security phase.
• A vendor's integration lead.

Bad candidates:

• One-off external reviewers on a single project.
• Internal teammates — they belong on the team page as workspace members, not in the address book.
• Anyone you want to grant access to. The address book doesn't do that.

Privacy #

Contacts are scoped to the workspace. Other workspaces can't see this list. Removing a contact does not affect their existing stakeholder portals on any project — those are separate records keyed by token, not by address-book entry.

Audit #

Add / edit / remove of an address-book contact is logged on the workspace audit log with the actor, the contact's email, and the timestamp. Useful for regulated verticals where "who knew about this engagement" is itself an auditable question.