Inviting Users
Workspace Admins and Super Admins grow the team by sending invites tied to a specific role (and optional designation). Invited users receive email with a secure link to join the same tenant everyone else uses.
Send an invite
- Go to Admin Settings → Team permissions.
- Choose Invite user (or equivalent).
- Enter email, display name, and the role that matches what they should be allowed to change.
- Optionally set a designation such as CSM, AE, SE, or a custom value your workspace uses for reporting slices.
- Send the invite. The user must accept before they appear as active.
Invites can be resent or revoked while pending. After someone accepts, manage them alongside existing users on the same Team permissions screen.
Roles at a glance
Pick the smallest role that still lets someone do their job. Full detail is in Roles and permissions.
| Role | Typical invite scenario |
|---|---|
| Super Admin | IT owner, billing owner, or security—full tenant control |
| Admin | RevOps or CS leadership configuring models, users, and notifications |
| Data Admin | Analytics engineer owning connections and queries without user administration |
| Manager | Team lead who reassigns accounts and needle movers but does not change global configuration |
| Account User | Individual CSM or AM working an assigned book of business |
| Renari User | Copilot-only access for people who should ask questions but not change configuration |
Avoid inviting the entire company as Admin; use Account user plus account assignment for frontline scale.
Account assignment and “My accounts”
Before people rely on Needle Movers, predictions, or portfolio views, make sure they have the right book of business:
- Per user — assign accounts to a person (or rely on fields on your Account model, such as
csm_email, so My accounts fills automatically). See Field reference. - Per shared team — under Admin → Team, use the Shared Teams tab to define teams (each has an External Team ID and a member list). Map your Account model’s
team_idproperty to a column whose values match those IDs. After an Account model refresh, every member of the matching team is auto-assigned to the account. Full workflow: Shared teams. On the same screen, the Team Members tab is only for workspace users and invites—not for defining shared teams.
Many of those views default to My accounts. Confirm assignment rules early so new users see a populated portfolio on first login.
Single sign-on and auto-provisioning
If your workspace enables SSO, users may auto-join the first time they authenticate with an email domain your admin has approved—skipping manual invites for large rollouts. Domain rules and default roles are configured in SSO.
Mixed mode is common: executives SSO in while contractors stay on email invites.
Deactivation
- SSO users — access is ultimately controlled by your identity provider. Remove or disable the user there so they can no longer authenticate into FunnelStory.
- Manually invited users — remove them by deleting the user from Admin Settings → Team permissions.
Deleted or IdP-removed users retain historical attribution on comments and audit entries where the product preserves it.