Surfaces, roles and current terminology

Permissions, settings and activation

• Use an Admin role or a staff role granted the exact Users and Roles permissions required.
• Treat role-list access, edit, deletion, impersonation, and login-history access as separate privileges.
• Restricted staff must see only permitted sections; a configured Admin URL does not bypass authorization.
• Deletion and impersonation are sensitive operations. Verify the target account and business ownership first.

Core workflows

Find and maintain an account

1. Open the configured Admin URL and choose the matching role list: Students, Instructors, Organizations, or Admins.
2. Filter or search for the account, then open its detail or edit action.
3. Review role, status, organization ownership, and recent login history before changing access.
4. Save the change and verify the user reaches only the intended surface.

Apply restricted staff access

1. Open Users ? Roles and select or create the staff role.
2. Grant only the required list, view, edit, deletion, impersonation, and history permissions.
3. Assign the role to the staff account.
4. Test with that staff account at the configured Admin URL.

Delete or impersonate safely

1. Confirm the exact user and check linked learning, sales, organization, or authored content.
2. Use impersonation only to reproduce the user's view; exit the impersonated session before other admin work.
3. Use delete only when retention and ownership requirements are satisfied.
4. Recheck lists and audit context after the action.

Result states

• Success: The account appears in the correct role list, intended permissions work, and restricted sections remain unavailable.
• Pending: Role, instructor, or organization approval is still awaiting an authorized reviewer.
• Denied: The staff role lacks the requested permission, or the target action is outside its scope.
• Error: A save or delete fails because of validation, linked records, session state, or a server error; preserve the account and investigate before retrying.

Operational notes

• Do not document a fixed admin prefix. Refer to the configured Admin URL and use /admin only as a default example.

Related guides

• User Roles
• User Groups
• Organization Users
• Security Settings