Skip to main content

​
Onboard a new teammate

A new rep starts Monday. Before they log in, the admin (or a manager) has to add them to Katalyst with the right role, walk through the Salesforce permission prerequisite, send the invite, and queue up a first-day handoff with the two Plays they should run on day one. About 10 minutes, mostly waiting on the invitee to accept the invite email.

​
What to expect

  • Timing. Roughly 10 minutes (most of it asynchronous, waiting for the invitee to accept).
  • Prerequisite. The admin (or a manager) has access to Manage Team. The new teammate has a Salesforce login already, and their Salesforce user has the Approve Uninstalled Connected Apps permission enabled (or the admin has the access to enable it on the Salesforce side before the new teammate tries to connect).
  • Outcome. The new teammate has a Katalyst seat with the correct role, can see their book the first time they log in, and has a Slack or message handoff naming the first two Plays they should run.

​
Step-by-step

  1. Open Manage Team. From the side nav, click the Settings entry labeled Manage Team. The page lands as a single workspace: the current members table on top with avatar, email, role, and per-row actions; the pending invitations table below (only renders when at least one is outstanding). The Invite Member button sits in the header.
  2. Click Invite Member; read the Before You Invite dialog. The first dialog is a Salesforce prerequisite walkthrough, not the invite form yet. The headline reads “Before You Invite” and the body walks through the Salesforce step the new teammate (or the admin) needs to take: Salesforce → Setup → Users → click the user → click their Profile → under System Permissions, check Approve Uninstalled Connected Apps. The collapsible “Don’t see the option?” chevron expands a fallback flow for orgs where System Permissions are managed via permission sets. Confirm this is done (or queue it to do), then click the “I’ve enabled it, Continue” button.
  3. Fill the Invite Team Member dialog. A second dialog opens with two inputs: Work Email Address and Role. The role select offers Member (the default, the right choice for a rep or CS lead) or Manager (the right choice for a sales manager or RevOps lead). Admin is intentionally not on this list. Read the inline help under the role select: Manager can manage team members and view all data; Member can view and work with data.
  4. Send the invite. Click Send Invite. The dialog dismisses, a success toast fires, and the new teammate’s row drops into the Pending Invitations table at the bottom of the page. The invite email lands in their inbox within a minute or two; the link in the email walks them through Katalyst’s onboarding flow when clicked.
  5. Wait for the invitee to accept. Acceptance is asynchronous; the new teammate has to open the email, click through, sign up, and complete the Salesforce OAuth handshake. While waiting, the admin can move on. When acceptance lands, the row moves out of the Pending Invitations table and into the Current Members table.
  6. Confirm the role on the first member-table render. When the new teammate appears in the Current Members table, glance at their Role column. If it landed as Member but should have been Manager (or vice versa), click the role dropdown on their row and switch it. The page mirror-writes the change to both Clerk and Salesforce-dependent surfaces, then full-reloads to make sure the new role takes effect everywhere.
  7. Drop a first-day handoff. Send the new teammate a Slack or message handoff with two starting Plays: Build your daily focus list (so they learn the morning ritual on day one), and Start the day with Signals (so they see what Katalyst surfaces about their book before opening Opportunities). Include the link to Connectors so they know where to land if their Salesforce, Gmail, or Calendar connection needs reconnecting.

​
Variations

If the new teammate is a manager (sales manager, RevOps lead, CS lead with team-visibility needs), pick Manager in the role select instead of Member. Managers can see every rep’s book on Opportunities and Accounts, can run the All Opportunities and All Accounts scopes on AI Activity, and can run cross-rep audit Plays like Weekly close-the-loop review. If the org has its own Salesforce SSO and the admin is not sure whether the Approve Uninstalled Connected Apps permission is set, queue the SF-side step first (either do it as the admin or message the Salesforce admin), then return to send the invite; the invite step itself does not verify the permission, so an invitee whose SF profile is missing it will silently fail to connect Salesforce on their first run.
A dedicated screenshot of the Manage Team page (manage-team.png) is pending. When it lands, it should anchor step 1 (the member table plus the Invite Member button) and step 2 (the Before You Invite Salesforce-prereq dialog with the chevron expanded). A future product page at ../product/setup/team-and-permissions is also pending; this play references the surface in prose until that page lands.