Role Based Access Assignment

Frontegg manages who can do what inside a B2B SaaS product through roles and permissions tied to each account. A Beam agent reads a new user's signup details, such as their email domain and invitation source, and applies the customer's approved rule for which role fits, for example matching a company email domain to an account's default role, then updates the user's permissions in Frontegg. It notifies the account admin that a new member has joined. Signups with no clear domain match, a request for an elevated role like admin, or an invitation from an unrecognized source are held for a person to assign manually.

Tenant Account Provisioning

A new B2B customer using Frontegg needs its own tenant set up with the right plan limits and settings before anyone can log in. A Beam agent reads a new customer record from a connected billing or CRM system, applies the customer's approved rule for tenant configuration, such as seat count and enabled features matching the plan purchased, and sets up the tenant's initial settings in Frontegg to match it. It updates the linked record to confirm the tenant is ready. Custom contracts, mid cycle plan changes, or any configuration outside the standard plan tiers are left for a person to set up directly.

Inactive User Cleanup

User accounts in Frontegg accumulate over time, including people who left a customer's team or never completed signup. A Beam agent reads each account's last login date and current status, applies the customer's approved rule for what counts as inactive, such as no login for one hundred eighty days, and updates the account status to suspended so it stops counting against seat limits. It keeps a note of the last login date for reference. Accounts belonging to an admin, tied to an active billing seat dispute, or reactivated shortly before the check are left active for a person to check before any change is made.