Invite a teammate

Once your application is sending events, bring the rest of your team into Beacon so they can see the data and act on it. Invitations are sent by email; the recipient creates their own password and joins your organization.

Who should I invite?

Common roles on a Beacon-using team:

  • Developers integrating the SDK into other applications.
  • Product managers reading retention, funnels, and usage insights to inform roadmap decisions.
  • Support engineers triaging the Invalid Events page and exception reports.
  • Founders / CTOs monitoring overall product health.

Beacon doesn’t charge per team member on any plan — invite as many people as you need.

Step 1 — Open the User Management page

In the sidebar, expand Settings and click Users. You’ll see a table of everyone currently in your organization, including yourself.

Step 2 — Send the invitation

Click Invite User in the top-right. A modal appears with two fields:

FieldRequiredNotes
Email addressYesThe invitee’s email address. They’ll receive the invitation here. Each email can only belong to one Beacon account, so the address must not already be registered elsewhere.
RoleYesWhat the invitee can do once they accept. The dropdown lists every role configured for your organization — see Roles below.

Click Send invitation. A green toast confirms “Invitation sent to email.” The new user appears in the table immediately with a status of “Invited.”

Roles

The Role dropdown lists every role configured for your organization. By default a fresh organization has at least one administrator role (granted to the account creator), and you can define additional roles in Settings → Roles.

Each role is a named bundle of permissions — view dashboards, manage products, manage API keys, invite users, manage billing, and so on. Pick the role that matches what the invitee needs to do; you can change it later if you got it wrong.

The role can be changed from the user table at any time (each row has a “Change Role” action for users with the manage_tenant_settings permission).

Step 3 — The invitee accepts

The recipient gets an email with the subject You’ve been invited containing a link to accept.

Clicking the link takes them to a page where they enter:

  • Display Name (optional) — what shows up on team rosters and the header avatar.
  • Password — minimum 12 characters.
  • Confirm Password — the same value again.

On submit they’re logged in immediately and see your organization’s dashboard.

If they don’t accept, you can resend the invitation. Each “Invited” row in the user table has a Resend Invite action that issues a fresh email.

Common questions

The invitation email never arrived. Have the invitee check spam. If it’s truly missing, click Resend Invite in the user table — that issues a new link. If it still doesn’t arrive, the email may be blocked by the recipient’s provider; ask them to allow softagility.com mail or contact support@softagility.com.

I’m getting “This email cannot be invited.” For privacy reasons, Beacon doesn’t distinguish “this email is already in your organization” from “this email is registered with a different organization.” If the email is already in your team, check the user table. Otherwise, the recipient is on Beacon under a different organization and can’t accept your invitation — they’d need to use a different email address.

Can I disable a user instead of removing them? Yes. From the user table, click Disable on their row. They lose access to your organization immediately but their audit trail is preserved. Enable restores their access.

The user accepted but can’t see the dashboard / can only see a few pages. Their role doesn’t grant the relevant permissions. Open their row and click Change Role to upgrade them, or define a custom role that fits their responsibilities.

What’s next

You’ve finished First Setup. Your application is sending events, your team has access, and you’re ready to start exploring data.

The next section — Exploring Your Data — walks through the Overview dashboard, Event Explorer, Property Explorer, and Sessions in detail.