Users and groups
A user is a person in the system. In a specific company or space, the person appears through membership in that company space. This membership carries the role, state, and metadata used for management and reporting.
Roles in a space
Section titled “Roles in a space”| Role | Typical meaning |
|---|---|
owner | Space owner. Should not be left without a replacement. |
admin | Manages users, groups, content, and operational settings. |
student | Ordinary e-learning participant. |
participant | Participant in specific scenarios, often events or courses. |
Membership states
Section titled “Membership states”| State | Client-facing meaning |
|---|---|
invited | The user was invited but is not active yet. |
pending | Transitional state waiting for a process to finish. |
active | The user is active and can work in the space. |
revoked | The user is archived or removed from the space. |
A revoked user is not deleted like an ordinary object. Study history, reporting, and audit links must remain traceable.
Groups
Section titled “Groups”Groups are used for:
- organizing users,
- bulk content assignment,
- distinguishing e-learning and blended learning scenarios,
- group leaders,
- invitation links and self-service entry.
Common tasks
Section titled “Common tasks”| Task | What to check |
|---|---|
| Invite a user | E-mail, role, state, and company-space membership are correct. |
| Import users | Identifier mapping is stable and failed rows are reviewed. |
| Add a user to a group | The user receives group-based learning if the group has assigned content. |
| Remove a user from a group | Learning state is checked because assignment sources can change. |
| Revoke a user | The user no longer participates actively, but historical reporting remains available. |
| Change a role | The new role matches what the person should manage or view. |
Recommended client rule
Section titled “Recommended client rule”A group should have a clear purpose. If one group means department, course, project, and access level at the same time, reporting and automation become hard to reason about.
Screenshot needs
Section titled “Screenshot needs”- user list with filters,
- user detail with role, state, and metadata,
- group detail with members,
- group detail with assigned content.
Edge cases
Section titled “Edge cases”- The last owner of a space should not be revoked without a replacement.
- A global user can be a member of multiple spaces.
- E-mail may not be the best long-term identifier.
personal_idis often more stable for integrations. - Adding or removing a user from a group can change their learning tasks.