Team settings

Updated May 2026

You'll learn how to: Invite new teammates, manage their roles, see the audit log of what owners and admins have done, and configure how records are shared by default.

Time: 5 minutes to invite your first teammate. Configure-once for the policies.

Prereqs: You're an owner or admin on a plan that includes multi-seat (most paid plans). Members can see most of this in read-only mode.

Open Team settings

In the left sidebar, click the gear icon for Settings. Click the Team tab.

The Team tab is divided into four panels:

Team Settings: roster, invite, roles.
Team Admin Signals: incomplete onboarding, missing integrations, follow-up gaps across the team.
Team Audit Log: a chronological log of every owner / admin action.
Workspace Sharing Policy: who can see which records by default.

Invite a teammate

In the Team Settings panel, click Invite Teammate (or the equivalent + button).

Fill in:

Email address. Required. The invite goes to this address.
Role: Owner, Admin, or Member. (See role definitions below.)
Initial pipeline access: which pipeline(s) they see by default. You can change this later.
Optional personal message that appears in the invite email.

Click Send. The invitee receives an email with a join link. Once they click it and sign up, they're added with the role you picked.

Pending invites appear in the roster with a "Pending" badge. You can cancel a pending invite or resend the email from the row's more-actions menu.

The three roles

Owner: full control. Can change billing, transfer ownership, add and remove other owners, see and edit every record in the team. Usually 1-2 owners.
Admin: most administrative actions but cannot change billing or remove owners. Can invite and remove members and admins, edit any record, see the audit log.
Member: works in the team day-to-day. Cannot invite, manage roles, see the audit log, or delete records that belong to others (unless the sharing policy is set to allow it).

You can promote a member to admin or demote an admin to member from the row's more-actions menu. Changes are logged in the audit log.

Remove a teammate

In the roster, click the row's more-actions menu and pick Remove. A confirmation dialog asks what to do with the records they owned:

Transfer to another teammate: pick who. The receiving teammate becomes the new owner of every record the removed person owned.
Reassign to primary owner: defaults to you (or the primary owner).
Leave unassigned: not recommended; orphaned records vanish from owner-filtered views.

Click Remove. The user is removed and their session is revoked.

Admin signals

The middle panel surfaces team-wide health issues an owner or admin should know about:

Onboarding gaps: teammates who haven't completed onboarding or who skipped key steps.
Integration drift: teammates whose Gmail / Calendar / LinkedIn connections have broken and need reconnecting.
Follow-up gaps: contacts on someone's rhythm list who haven't been touched in much longer than the rhythm cadence.
Stalled deals: opportunities on a teammate's pipeline with no activity for 14+ days.

Each signal links to the relevant teammate or record so you can take action without leaving the Team tab.

Audit log

A chronological feed of admin and owner actions:

Member invited / removed.
Role changed.
Sharing policy changed.
Team-wide settings changed.
Bulk delete or merge actions over a certain threshold.

Each entry shows who did what, when, and (for bulk actions) the scope of the change. Useful for retrospectives and compliance.

The audit log is owner / admin only. Members don't see it.

Workspace Sharing Policy

The fourth panel controls who can see what by default. Choose one of:

Private to owner: every record is private to the teammate who created it. Other teammates only see records they're explicitly added to (e.g. as collaborators on a deal).
Team-visible (recommended for most teams): every record is visible to every teammate by default. Owners can still mark specific deals as private for sensitive opportunities.
Read-by-team, write-by-owner: everyone can see everything, but only the record owner (or admins) can edit.

Picking the wrong policy at the start creates a lot of friction later (e.g. starting with Private and then needing to bulk-share when the team grows). The default for paid plans is Team-visible.

Two-factor and SSO

For teams on the Business or Enterprise plan, additional settings appear:

Require 2FA for all teammates: turn on a team-wide requirement. Teammates who don't have 2FA enabled are prompted at next sign-in.
SAML SSO: configure SAML so teammates sign in via your identity provider. Once enabled, individual email / password sign-in is disabled.

These options sit at the bottom of the Team tab on plans where they're available.

If something goes wrong

Symptom: "Invite button is greyed out." → Fix: Your role isn't owner / admin. Ask an existing owner / admin to either invite the person directly or elevate your role.
Symptom: "Invite email never arrived." → Fix: Check the invitee's spam folder. The sender is noreply@nynch.com. From the roster, you can resend the invite. If still nothing, ask them to sign up directly at app.nynch.com and you can add them from the roster afterwards.
Symptom: "Pending invite for an email that already has a Nynch account." → Fix: The invitee already has a Nynch login. Cancel the pending invite, then send a fresh invite; this time they'll be added without needing to sign up.
Symptom: "I demoted myself from owner by accident." → Fix: Demotions don't take immediate effect on the sole owner. There must always be at least one owner. If you genuinely demoted yourself and another owner exists, ask them to promote you back. If you're sole owner, the demotion was rejected and you should still be owner.
Symptom: "Audit log is empty." → Fix: New teams have no audit entries yet. The log fills as owners / admins take actions.
Symptom: "Sharing policy change didn't seem to do anything for existing records." → Fix: Sharing policy applies to records created AFTER the change. Existing records keep their previous visibility. Bulk-update existing records via the Contacts / Deals table if you need to retroactively change them.