Surfaces, roles and current terminology

Permissions, settings and activation

• The signed-in account must be an organization owner or have organization-management access.
• Instructor and student creation or assignment must remain within package counts and expiry.
• Organization users can manage only records owned by or assigned to their organization.
• Platform administrators handle cross-organization corrections from the configured Admin URL.

Core workflows

Add an instructor or student

1. Open Panel ? Organization and choose Instructors or Students.
2. Review the current package capacity before adding a member.
3. Create or link the user with the correct role and organization ownership.
4. Confirm the member appears in the organization list and can access the intended panel.

Resolve a package limit

1. Open Packages and compare used capacity, total capacity, and validity.
2. Remove an incorrect pending assignment only after confirming ownership.
3. Assign or purchase additional capacity through the available package flow.
4. Retry the member operation after the package becomes active.

Transfer operational responsibility

1. Identify the current organization owner and affected linked records.
2. Have a platform administrator make any cross-organization ownership correction.
3. Verify instructors, students, courses, and access remain under the intended organization.
4. Test with the organization account after the change.

Result states

• Success: The member is linked to the correct organization and package usage increases as expected.
• Pending: An invitation, package purchase, payment, or administrative ownership correction is incomplete.
• Denied: The account is outside the organization scope or the package has no available capacity.
• Error: Duplicate identity, invalid role, expired package, or inconsistent ownership blocks the operation; do not create a second account as a workaround.

Related guides

• Organization Users
• Panel Overview
• Subscription Packages
• Admin Users Operations