StartupKit
EN

Team Access Control

Give each team member the right level of access to Hiring, Security, Outreach, Training, and Performance, and audit or revoke it when they leave.

Why It Matters

Not everyone on your team needs to see everything. Your recruiter doesn’t need vulnerability reports; your security lead doesn’t need outreach campaigns. Team access control lets you decide, per person and per product, who can view, who can manage, and who stays out, and gives you a single page to answer “what exactly can this person access?” when audit or offboarding time comes.

Products and Access Levels

Kit has five products: Hiring, Security, Outreach, Training, and Performance. Each team member gets one access level per product:

Level What it means
No access The product is off-limits. Opening it shows an access-denied screen with a way to request access.
Member Standard day-to-day access: view and work with the product’s content, subject to any per-item assignments (e.g., restricted job postings).
Admin Full control of that product: create, configure, and manage everything in it, without needing per-item assignments.

If you never set a level for someone, they’re a Member. Existing team members keep working as before; nothing gets locked out until you decide to change it.

Account Admins sit above product levels: they see every product, access everything, and are the only ones who can change an existing member’s access. An Admin can also hand out the invite members capability, which lets that person set the access of the teammates they invite, never above their own.

Note

Product levels control access to a whole product. Within a product, finer-grained assignments still apply; for example, restricted job postings are visible to their assigned hiring team, account admins and Hiring admins. See Inviting Your Team for how job-level roles work.

Note

Finance is the exception to the product matrix. A Finance member starts with No access in all five products, but can use the focused Finance workspace for candidate payouts, researcher disbursements, and W-8/W-9 review. Those queues expose payment context, not candidate applications or vulnerability-report content. See Team Roles.

The Modules Matrix

Go to Settings → Team → Modules for the whole-team view: one row per member, one column per product. Choose a role or adjust product levels, then select Save on that member’s row.

Two shortcuts speed this up:

  • Roles: each row has a picker with predefined team roles like Recruiter, Finance, Security Analyst, Growth, Trainer, or People Lead. Picking one fills levels across all five products; adjust individual cells before saving.
  • Admin role: choosing Admin grants account-wide authority when saved. Individual product controls are disabled for account admins. The account owner’s row is read-only.

Tip

Start from a role, then tweak. Roles encode the levels most teams use: Recruiter gets Hiring admin plus member access to Outreach, Training, and Performance; Security Analyst gets Security admin plus Training and Performance. It’s faster and less error-prone than setting each module by hand. See Team Roles for what each role covers.

The Member Access Page

For a single-person deep dive, go to Settings → Team → Members and click a member. Their access page shows:

  • Role: their team role, from full Admin down to Member
  • Product levels: their level for each of the five products, editable in place
  • Invite members: a toggle that lets this person invite teammates at or below their own access, without making them an Admin. See Inviting Your Team
  • Access ledger: a read-only list of their assignments and individual grants: which job postings, which reports, which campaigns, and since when

Reading the access ledger

The ledger collects assignments and individual grants across five products. It is not a complete list of every open item the person can view through module access. Each entry names the item, the product it belongs to, and the date access was granted. Use it to:

  • Prepare for a security or compliance audit
  • Double-check a contractor only sees what they should
  • Review everything a departing member touches before offboarding

To restrict a single report or campaign to a chosen few and grant them a view or manage role on it, see Item-Level Access.

Company Teams and Pulse Audiences

Company teams describe who works together; they do not grant product access, administration or manager authority. You can choose an ordinary primary team yourself. Restricted teams require an admin assignment, although existing members can leave them. Changes apply now to future Pulse confirmations, never to already-confirmed audiences or historical results.

For new-policy Pulse rounds, current Performance access is necessary but is not enough to read every team’s history:

Content Additional access rule
Releasable closed numeric result Submitted a rating in that round, or currently a Performance admin; at least five ratings are still required
Closed conversation and shared commitment Originally invited to that round, or currently a Performance admin; rating is not required

Both require sign-in. Forwarded links, self-service team moves and replacement memberships cannot grant historical access. Private audience and participation permissions are not a manager-facing respondent checklist. Anonymous post ownership is not revealed to workspace admins; they may remove content without learning the author.

New rounds and their access records expire 24 months after the shared close. Revocation immediately blocks reading and responding; removing the membership deletes its private permissions and post ownership without recalculating the aggregate. Earlier workspace-wide rounds keep their original access, link, no-comments and retention rules. See Team Pulse.

Mute a member’s notifications

Some people belong to the workspace without working in it every day: a CEO who wants access but not the stream, or a stakeholder who drops in once a quarter. Instead of asking them to tune their own preferences, an admin can mute them for this workspace.

  1. Go to Settings → Team → Members and open the member
  2. In the Notifications card, click Mute

Muting stops every notification Kit would send them from this workspace: in-app, email, Slack DMs, text messages, digests, reminders a teammate set for them, onboarding emails, and performance review reminders. Slack channel posts still name them, without an @-mention. Work that would have nudged them, such as a stalled candidate, goes to the rest of the team instead, as it does during Holiday Mode. Their other workspaces are unaffected.

A few things still arrive: calendar invitations for interviews they’re on, reminders they set themselves, security notices (privilege changes, new members joining, ownership transfer, breach alerts, disconnected apps, CVs downloaded from outside the company, bounty payouts that need a second look) and on-call pages. To stop on-call pages, remove the person from the on-call rotation.

The members list shows a Muted badge, and the member sees a banner naming who muted them on their notification settings pages. Click Unmute on the same card to restore delivery. Only admins can mute or unmute.

Requesting Access

Open Access requests, or choose Request access from an access-denied screen or MCP Setup. Select the module and level, then explain the blocked task in 20–2,000 characters. Kit and AI-agent requests enter the same admin inbox; sending one does not change access.

Kit’s built-in assistant links to the access-request form, where you must be signed in. Enter, review, and submit your explanation there. Native chat does not submit access requests or notify admins. An external MCP client with your delegated OAuth access can submit a request and notify admins when you ask it to.

Account admins review the explanation and exact grant, then approve or decline in Access requests. A decline requires a note. Members can track the decision or withdraw a pending request. Approval changes the requested module permission; an AI connection still needs its own OAuth consent. See Requesting and Reviewing Access for the complete workflow.

Offboarding a Member

When someone leaves, open their member access page. You have two options:

Action What happens
Revoke all access Keeps their seat but strips every product level and every individual grant in the ledger. Good for leave-of-absence or role changes.
Remove from account Removes them from the team entirely.

Either action also clears the invite members capability, so a delegated inviter loses it along with their product levels.

Pending access requests are withdrawn into history. They cannot be used to restore a revoked or removed membership.

If the person is the sole hiring manager on a posting or assigned to an active report, Kit requires a choice: pick a successor or explicitly leave the item unassigned. Only then does it revoke access or remove the member. The account owner cannot be revoked or removed through this flow.

Warning

Revocation strips everything at once and doesn’t keep an undo list. After “Revoke all access”, the member’s individual grants are gone; restoring them means re-adding each one by hand. Review their access ledger before revoking, and choose successors carefully during reassignment: once ownership moves, the previous owner is detached from those items.

Do / Don’t

Do Don’t
Use roles to set levels consistently across similar people Set every module manually when a preset role matches the person’s responsibilities
Review the access ledger before offboarding Remove a member blind; sole-owned items will force a reassignment prompt anyway
Use “Revoke all access” for leave or role changes Remove someone from the account when they’re coming back
Leave levels unset for members who need standard access Set “No access” everywhere as a default; that’s what revoke is for

Quick Checklist

  • Open Settings → Team → Modules and review every member’s row
  • Apply roles for common jobs, then fine-tune individual cells
  • Assign the Admin role only to people who manage the team
  • Spot-check a member’s access page and ledger to confirm it matches expectations
  • Show your team how to explain blocked work in Access requests and track the decision
  • At offboarding: review the ledger, pick “Revoke all access” or “Remove from account”, and assign successors for sole-owned items

Type to search...