Manage Organization Members and Member Limits - Article
Summary
Organization membership connects people to the customer, partner, department, or branch they belong to. Maintain those relationships accurately so that local administration, learning visibility, and organizational processes apply to the intended people.
Use this article to:
- Add existing users or create new members.
- Maintain suborganization assignments and shared memberships.
- Distinguish membership removal from account-level changes.
- Set member limits and understand how parent and child capacity interact.
Understand what membership changes
An organization relationship can affect what a person sees, who may manage them, and which organization-based processes apply. It does not replace their role, and it does not by itself mean they are enrolled in a Training Activity.
Where automatic enrollment or onboarding is configured, adding a member can also lead to learning assignments. Check that configuration before adding a large group. A routine membership import can otherwise become an unexpected enrollment event.
People can belong to several organizations or suborganizations. Use that deliberately for shared responsibilities, not as a workaround for an unresolved access problem.
Work with the member list
Open Organizations, then select the organization. The member view provides search, filters, membership information, and permitted actions.
| Element | Purpose | Useful interpretation |
|---|---|---|
| User | Identify the person's account and email address. | Confirm identity before editing or removing a similarly named person. |
| Role | Understand the user's system role. | Role and organization membership are separate; adding a person does not automatically make them a Manager. |
| Registered | Show the account's registration date. | Do not treat this as the date the person joined the organization. |
| Suborganization | Show the relevant branch assignments. | A parent view can include people from its subordinate structure. |
| Search and Filters | Narrow the population before reviewing or taking action. | Available filters depend on configuration. Check active filters if someone appears to be missing. |
| Row actions | Edit the user, manage suborganizations, share files where available, or remove the organization relationship. | The available actions depend on role and scope. |
| Bulk actions | Apply supported operations to selected members, such as removal or transcript retrieval. | Review the selected population before proceeding. |
The organization list shows an active-member count, which excludes blocked accounts. The organization's member view can include blocked accounts, so the totals may differ. A blocked person has not necessarily been removed from the organization.
Some filters persist during your session. The suborganization filter is specific to the organization being viewed and resets when you navigate to a different organization. Recheck the filters before a bulk operation.
Add an existing user
- Open the intended organization.
- Select Add member → Add existing.
- Find and select the correct existing account within your permitted scope.
- Complete the action and verify the person in the member list.
- Assign the appropriate suborganization if needed, then check any organization-driven learning assignments.
Use an existing account when the person already uses the platform. A second account can divide their learning history, certificates, and support context.
If an existing user cannot be found, check your search, role, and organizational scope before creating another account. A central administrator may need to handle a legitimate cross-organization assignment.
Create a new user or invite the person to join
Use Add member → Create new when an authorized administrator should create the account. Complete the required profile fields and the account-communication options shown by your platform, then verify the organization relationship.
Use Add member → Invite by email when the person should complete the entry process themselves. Invitation and registration behavior is covered in Invite Users and Assign Organization Membership.
These routes solve different operational needs. Creating an account is not the same as sending an invitation, and sending an invitation is not evidence that the person has accepted it and joined.
Delegate local role management where enabled
Eurekos support can enable an option allowing Managers to change users between Participant and Manager within their own organization, or create a new user directly with the Manager role. This can let a customer coordinator appoint another local coordinator without requesting every change from the central team.
This is an optional, specifically scoped permission—not a default consequence of organization membership and not permission to assign any platform role. Agree who may appoint Managers and review the person’s other memberships before changing a shared account. If the option is unavailable, ask the responsible administrator to handle the change or discuss the delegation requirement with Eurekos support.
Maintain suborganization assignments
Use the member's Manage suborganizations action to review or change branch assignments. Inspect the full path when several branches share the same name.
Before changing a person's assignment, decide whether the new relationship should replace an old one or exist alongside it. A regional specialist may legitimately support two branches; a transferred employee may no longer need the previous branch relationship.
After the change, check the resulting memberships, relevant learning access, and local management scope. If an external identity or user-provisioning process maintains membership, coordinate the change there as well so that a later synchronization does not reverse it.
Remove membership without confusing it with account status
| Action | What it changes | When to use it |
|---|---|---|
| Remove from organization | Removes the relevant organization relationship rather than deleting the account. | The person no longer belongs to that business population. |
| Remove a suborganization assignment | Changes the person's branch relationship. Other memberships may still apply. | A local responsibility or branch assignment has ended. |
| Block the user account | Changes the account's ability to access the platform. | An authorized account-level access decision is required. This is broader than leaving one customer organization. |
| Delete the user account | Uses the platform's account-deletion process. | Follow the applicable user-management and data-retention procedure; do not use it as a substitute for a membership change. |
Removing a person from a parent organization or higher-level branch also removes their relationships within its subordinate structure. Review the full scope before confirming.
For permitted Manager removal from a suborganization, a person with other suborganization memberships keeps those other relationships. When their only suborganization membership is removed through that flow, they are moved to the parent organization. Therefore, leaving a branch does not necessarily mean leaving the wider organization.
Manager removal, editing, and blocking permissions can be configured separately. Shared memberships can restrict the ability to edit a person, and account-status controls may require the Manager to manage all of that user's organizations. If an action is unavailable, escalate the membership task rather than granting unnecessary account-wide authority.
Configure member limits
Open the organization or suborganization Settings → General and use Members limit to restrict new membership within that scope.
A member limit controls organization capacity. It is not an activity seat limit, a limit on simultaneous users, or a learning-completion target.
| Situation | How the limit works | Example |
|---|---|---|
| A person belongs directly to an organization | They occupy one place in its limit. | A limit of 100 with 40 members leaves capacity for 60 additional people. |
| A person belongs to a suborganization | They count toward the branch limit and the relevant parent limit. | A new member in a regional branch uses capacity in that branch and its parent organization. |
| The same person belongs to two branches under one parent | They occupy one place in the parent's limit, not two. | A parent limit of 5 with one person assigned to two branches has 4 parent places remaining. |
| A branch reaches its own limit | It cannot accept more members merely because the parent has spare capacity. | A branch capped at 20 remains full even if the parent has 50 unused places. |
| The parent reaches its limit | Additional people cannot be admitted simply by selecting another branch. | The total capacity applies across the parent's structure. |
| A person already belongs within a full organization | They can still be assigned to a suborganization, subject to that branch's capacity and permissions. | Moving existing staff into a newly established department does not create another person in the parent's population. |
| A proposed limit is lower than existing membership | The platform does not allow the limit to be reduced below the existing population. | Resolve the membership or agree a suitable limit before saving. |
For example, a customer agreement may permit 100 members overall, with a local branch limited to 25. Those are nested limits, not separate allocations that create 125 places. The branch population contributes to the parent's total.
Do not infer available capacity solely from the active-member count shown on the main list. Review the member population and the platform's limit validation, particularly where blocked accounts or shared memberships are involved.
Practical membership patterns
| Requirement | Recommended approach | Outcome |
|---|---|---|
| A customer hires a new employee | Add the correct existing account or create/invite a new one; assign the customer branch. | The employee enters the correct administrative and learning context. |
| An employee transfers departments | Review whether to replace or retain the old assignment, then update the branch relationship. | Local oversight follows the employee's actual responsibilities. |
| A consultant supports two partners | Maintain deliberate membership in both partners and verify the required scope. | One account can support the legitimate shared relationship. |
| A customer has a capped membership agreement | Set the parent limit and add branch limits only where separate local caps are needed. | Delegated administration operates within the agreed capacity. |
Verify the setup
| Scenario or check | Expected result or evidence |
|---|---|
| Correct identity and placement Open the person's membership and branch path. | The intended account belongs to the intended organization. |
| Shared memberships Review all relevant relationships after a move or removal. | Required memberships remain; obsolete ones are removed. |
| Capacity Try the intended membership scenario with an authorized test account. | Parent and branch limits apply as designed. |
| Resulting learning Inspect any configured automatic assignments and participant access. | Membership leads to the intended learning outcome, without duplicate or unintended enrollment. |
Troubleshooting
| What you observe | What to check |
|---|---|
| Add member is unavailable or an addition is rejected | Check role, organizational scope, parent capacity, and the target branch limit. |
| A person remains visible after removal from a branch | Check their other memberships and whether the permitted removal flow moved them to the parent. |
| A Manager cannot edit one member but can edit others | Review that person's shared memberships, Organization filter, and Manager permissions. |
| A previously removed person is not automatically re-added by email mask | Manually removed email-mask-assigned users are not automatically re-added by the same matching rule. Add them deliberately if the relationship should be restored. |
| Members have not received expected training | Check that automatic enrollment or onboarding is configured; membership alone is not enrollment. Allow the configured background processing to complete. |
FAQ
-
Does removing an organization member delete their user account?
No. Removing membership removes the organization relationship, not the user account. Removing membership at a parent level also affects relationships within its subordinate structure. Review any other memberships separately; account blocking and deletion are different operations.
-
Does one person in two branches use two places in the parent member limit?
No. The same person occupies one place in the parent organization limit, even when assigned to two of its branches. Each branch still has its own applicable capacity limit. Parent and branch limits are nested limits, not separate allocations to add together.
-
Why does the organization list show fewer members than the member page?
The organization list shows an active-member count that excludes blocked accounts. The member page can still include blocked users. Do not use the active count alone to infer remaining capacity; check the relevant member limit and platform validation.
-
Does joining an organization automatically enroll a member in training?
Not by itself. Organization membership and Training Activity enrollment are different relationships. Learning is assigned automatically only when an organization Activities setting, onboarding rule, or other approved process is configured. Allow for any background processing.
-
Can a Manager appoint another Manager within their organization?
Yes, if Eurekos support has enabled the specific permission. A Manager can then change users between Participant and Manager within their own organization, or create a new user with the Manager role. This is not unrestricted role administration or a default consequence of membership. Review shared memberships and follow the agreed local delegation policy.