Skip to main content
Implementation Guide · Module 9 of 9 · ~10 minutes

​
Why this matters

Configuration is only valuable if people use it. How you introduce Endgame to your team shapes their first impression and determines whether they come back. This module covers the practical steps for inviting users and setting expectations so they get value quickly.

​
What you’ll do

  • Understand how user access works
  • Invite your first wave of users
  • Set expectations and share starting points

​
How access works

Endgame uses WorkOS to power authentication. Only Admins can manage user access from the User Management page in Settings. There are three ways to grant access:
  • Invite users - Send email invitations to specific users and assign them a role (Admin or Member). You can monitor which users have accepted invitations from the user management page.
  • Verified domains - Add and verify your company’s domain (e.g., acme.com) so that anyone with a matching email address can log in and be provisioned automatically. Domain ownership is verified through DNS TXT records.
  • Single sign-on (SSO) - If available for your organization, enable SSO so users authenticate through your preferred identity provider. You must verify your domains first before configuring SSO.
SSO is not available to all organizations. Contact support@endgame.io if you’re interested in enabling it.

​
Walkthrough

1

Decide your rollout approach

Two common patterns:Power users first - Start with 3-5 reps or managers who are tech-forward and will give you honest feedback. They help validate your configuration in real workflows and become internal advocates. This is the most common approach.Team-wide launch - If your configuration is solid (you felt confident in Module 8), you can invite the full team at once. This works best when paired with a brief kickoff session.
2

Invite users or set up domain access

Navigate to Settings > Users and choose your approach:
  • For a targeted rollout, click Invite User, enter each user’s email, and assign them a role (Admin or Member).
  • For a broader rollout, click Add Domain to verify your company domain. Once verified, anyone with a matching email can log in without individual invitations.
See the Authentication page for the full setup walkthrough, including SSO configuration.
3

Share the right starting points

When you invite users, point them to resources that get them productive fast:
  • Your First 10 Minutes - Walks them through profile setup, custom instructions, writing sample, and first prompts
  • Navigating Endgame - UI orientation for the home page, account list, account detail, and search
  • Your custom skills - Tell them specifically which skills you’ve built and when to use them (e.g., “Run the Pre-Call Brief skill before any customer meeting”)
The most effective admin rollouts include a short message (Slack, email) that explains why the team should use Endgame and gives them one concrete action to try. Something like: “We set up Endgame for the team. Try running the Pre-Call Brief skill on your next meeting account and see what you get.”
4

Set up a feedback channel

Create a way for users to report gaps or confusion. A Slack channel (#endgame-feedback), a shared doc, or just telling people to message you directly. The first two weeks of user feedback are gold for tuning.Common feedback you’ll hear:
  • “It didn’t know about [X field]” - Mark the field as important or create a rule
  • “The response didn’t match our methodology” - Upload the relevant knowledge doc
  • “It used the wrong term for [Y]” - Create a terminology rule
  • “I wish there was a skill for [Z]” - Build a new skill
5

Encourage personalization

Each user should set up their profile preferences including:
  • Role description - Helps Endgame tailor responses to their perspective
  • Custom instructions - Personal preferences for how they like information presented
  • Writing sample - Helps Endgame match their communication style
Users can also create personal skills for their own workflows. Encourage experimentation. Sometimes a rep discovers a pattern worth scaling to the whole team.

​
What to watch for in the first two weeks

After your team starts using Endgame, pay attention to:
  • Who’s coming back? Users who return within 7 days are on a good trajectory. If someone tries it once and doesn’t return, check in to find out why.
  • What are they asking? Common questions reveal which skills would be most valuable to build next.
  • Where are they confused? Repeated confusion points to a missing rule, knowledge gap, or terminology mismatch.

​
Checkpoint

You’ve completed this module (and the entire Implementation Guide learning path) when you’ve invited at least one user and shared a starting point with them. The real validation comes over the following weeks as your team adopts Endgame and you tune the system based on their feedback.

​
Go deeper

  • Authentication for the full guide on inviting users, domain verification, and SSO setup
  • User Management for details on roles, deactivating users, and managing access

​
What’s next

You’ve completed the Implementation Guide Learning Path. Your ongoing responsibilities as an admin:
  • Add knowledge as users request it or as you notice gaps
  • Build skills for your team’s most common and important workflows
  • Create rules when you spot terminology mismatches or data presentation issues
  • Review rules quarterly and whenever your CRM schema changes
  • Monitor usage to understand adoption patterns and identify users who may need help
The best Endgame admins treat configuration as an ongoing conversation with their team, not a one-time setup task. The more you tune, the more value your team gets, and the more they use it.

Previous Module

Test Drive