Adding member in a company or group

Here are the advantages in the same context as adding members to a company (invite path, force-add, and how the product uses them). Advantages of company membership overall Central roster: One place (/company → Members) lists who belongs to the organisation, their role, and status—easier than managing people only inside each course. Governance: Owner / Admin can invite, add, suspend, or drop members; Members get a controlled workspace without admin powers. Billing and capacity alignment: Seat checks on invite and force-add mean growth stays tied to what you pay for, so you do not silently exceed licensed capacity. Operational fit for training: Assignments, curricula, schedules, and (where used) compliance fields sit next to the member—good for workplace, SETA-style, or cohort programmes. Advantages of email invites (Overview → Invite members) Works for people who are not on the platform yet: You only need an email; they create an account or sign in and accept when ready. Explicit consent: Accepting an invite is a clear “join this company” step—useful for privacy, audit trails, and avoiding surprise access. Resilience: If email fails, you still get a backup invite link to share manually so onboarding is not blocked. Visibility: /company/invites gives a searchable queue (pending / accepted / expired / revoked) so admins can see what is stuck or expired. Advantages of “Add an existing user as member” (force-add) Speed: Skips invite-and-accept for users who already have an account—immediate ACTIVE membership when policy allows. Less friction for internal IT: Same-day access for staff who already use the LMS; no waiting on “find the invite email.” Transparency and exit: Default email with a one-click leave link supports trust and self-service removal; you can turn notification off if you must handle communication yourself (with the trade-off that they may not know they were added). Advantages of roles (Member vs Admin on invite/force-add; more on Members tab) Least privilege: Most people stay Members; only trusted people get Admin to change roster, billing-adjacent actions, or assignments—reduces accidents and misuse. Clear escalation path: Admins handle day-to-day; owner retains ultimate control of the company. Practical takeaway Use invites when people are new or external and you want a clear accept step and email trail. Use force-add when they already exist in the system and you need fast, controlled onboarding, still subject to billing active and seat rules.