Notification contacts

A notification contact is an email address that belongs to a project, a team, or the organization rather than to a person.

When something in that scope needs a human, the address gets a message. It keeps receiving after whoever set it up changes teams or leaves, which is the difference between this and a personal notification setting.

Where to set them

Contacts live in the settings of the thing they belong to, and each level covers more than the one below it.

Set on	Receives	Who can change it
A project (Project settings)	That project’s items	Anyone who can edit the project
A team (Team settings)	Items from every project in the team	Owners and admins, as for editing the team itself
The organization (Settings, then Organization, then Notification contacts)	Items from every project in the organization	Owners and admins, as for other organization settings

Which roles can do what is spelled out in Roles and permissions.

The levels add up. An item in a project reaches the project’s contacts, its team’s contacts, and the organization’s contacts. An address that appears at more than one level is mailed once, not once per level.

A project’s or team’s contact list also shows the contacts it inherits from the levels above it, read-only, so you can see what already reaches this scope before adding anything. Change those where they were set.

What arrives

One short email per item, containing the item, the project it belongs to, and a link back to Taiga.

The subject line carries the whole thing:

[Taiga][Acme Web] Review Initiatives

That is deliberate. The body is a courtesy for mail clients that show it, and it never contains document contents, findings, or code. Anyone who needs the detail follows the link and signs in.

Sending to a Slack channel

Slack can give a channel its own email address, so a notification contact is also how you get Taiga’s action-required items into Slack.

1. In Slack, generate an email address for the channel. Slack documents this under sending emails to a channel, and it is not available on every Slack plan. The address ends in slack.com.
2. In Taiga, open the settings of the project, team, or organization you want the channel to hear about, and find Notification contacts.
3. Paste the address and choose Send confirmation.
4. Back in Slack, open the confirmation message that appears in the channel and follow its link.

The channel then receives one message per item. Slack shows the sender and the subject and collapses the rest behind a click, which is why the subject line is written to be readable on its own.

One channel for everything is an organization contact. One channel per team is a team contact.

Confirmation

Nothing is ever sent to an address that has not confirmed.

Adding an address sends it a single confirmation link that expires after seven days. Until someone opens that link the contact sits in Awaiting confirmation and receives nothing, so an address typed with a typo goes quiet rather than mailing a stranger.

Opening the link confirms that the address works. It does not sign anyone in, and it grants no access to Taiga. That matters when the address is a Slack channel, because the link is visible to everyone in that channel.

If a link expires or goes astray, choose Resend on the contact to issue a new one. Issuing a new link invalidates the old one. A new link can be requested once a minute.

Which addresses are allowed

You can use any address on a domain your organization has verified, and any address belonging to a workspace or ticket system that publishes an intake address, such as Slack.

If your organization has verified no domains yet, any address is accepted.

An address that is refused says so, and names what would be accepted instead. The restriction exists because a notification contact is outside Taiga’s control once mail reaches it: whoever can edit a project can decide where its activity is sent. Every change to a contact is recorded in the audit log with who made it.

When delivery stops

Two states mean a contact is receiving nothing, and both are shown on the contact itself.

Awaiting confirmation means the link has not been opened yet.

Suppressed means the address bounced or reported a message as spam, and Taiga has stopped sending to it. This is worth watching for on a shared mailbox, where it is otherwise possible for everyone to assume notifications are arriving for months after they stopped.

Suppression applies to the address itself, not to the contact. Removing the contact and adding it again does not lift it: the new contact’s confirmation email is refused for the same reason. Fix the underlying problem with the address, then contact support to have it cleared, or use a different address.

Removing a contact

Remove the contact and delivery stops immediately, including anything that was queued for it and not yet sent.

Removing it changes nothing about the work itself. Every item still appears in the project’s inbox, which remains the system of record for what needs a person. A notification contact is a way of hearing about that inbox somewhere else, not a replacement for it.