Controlling Seat Allocations with SSO
WooNinja SSO supports the provisioning of seats to a user account so you can limit the number of users that can log into your system through a given SSO application. For example, let’s assume you sold 25 licenses to a company that uses Microsoft Azure as their SSO system. When set up, WooNinja will monitor the number of users that log in using Azure, and when the 26th person attempts to log in, they will be stopped:
Important
- Each application, e.g. Okta, MS Azure, can only have one assigned seat.
- Any reference to enrollments is for products (Courses or Bundles) assigned to that application.
To get started, open your SSO instance and click your name, then Backoffice
Click Seats, then Create Seat
Enter your seat details.
Title – This will appear as the banner on the ‘No Seats Available’ page.
Description – This will appear below the banner on the ‘No Seats Available’ page. We recommend you include contact details so that a user can reach out to you or their account representative to request more seats.
Max Seats – The total number of users who can log in using this application, e.g. MS Azure
Action – The action taken by the SSO system when a user is removed from a seat
- No Action
- Unenroll from Assigned Products – The user is unenrolled from any course or bundle which is assigned to the associated application.
- Unenroll from All Products – The user is unenrolled from any course or bundle to which they are enrolled in Thinkific
- Delete User Account – The user’s account in Thinkific is deleted. This is permanent and cannot be undone, with all progress lost. Be extremely careful if you choose this option.
Active – If the seat is active and counting users.
Unlimited – If the seat has no maximum limit on users.
Application – The application to which the seat is assigned.
Click Create Seat
You can view a seat and associated seat counts and users by clicking the ‘eye’ button next to it:
You can ‘detach’ a user from a seat using the ‘trash’ icon. However, this will not trigger any actions that are configured for the seat.
For your end users and clients, they can manage any assigned seats using the ‘Seats’ menu option, and then by choosing an application, they can remove a user. This removal action will trigger any action associated with the seat e.g. unenrollment from courses etc.
