video tutorial, we will go over the steps to set up affiliate within OASIS. Affiliate can be any institution or regions or district or any sort of entity that have their own behaviors and have their own coordinators to manage their own user and report. So to do that, log in as administrator and make sure that you have something to the dashboard called program or whatever you're referring to your entity as. In this example, by default, OASIS refer to entity as a program, but you can change your terminology to say we are breaking our users into, for example, regions. So when you name as region, you will show up as region just so that the terminology within OASIS will be consistent with what you use in your business. A typical example would be a district, a school, a program, a franchise, or any of those variety. Then you will see that there is already three entities created and we're just going to add one more. In this case, since we're calling it regions, we're going to say add a new region. Why add a new region? There's going to be a few attributes I'm going to set. One is the name of the region. So we can say this is going to be West Coast. The region code or whatever code that you're going to associate with it needs to be a unique string and it's very important if the system integrates with any external system for single sign-on or for reporting because the code that you enter here is the key, the link OASIS with the external system. So we can just say West, for example, as a code. You can set how many seats a region is allowed. This is in case you only give certain number of licenses to a particular entity. In this case, a particular region. You can say that the contract we have with them only give them 50 seats. Leave it empty. It should be unlimited. The next two fields are slightly complicated. The first one is learning path selection. By keeping it as allow, that means the coordinator for that entity is allowed to manage which course its own users are supposed to take. If you keep it as do not allow, that simply means administrator instead of the entity's coordinator, the system administrator will decide what courses a particular entity will have. This comes in handy, for example, if a particular entity, say West Coast, has purchased a hundred courses from you and every user within West Coast should have access to those course. You just simply set it as do not allow and then every user from West Coast will automatically get a hundred courses that they have signed up for. If you change to allow, that means when you make a hundred courses available for West Coast, the user within West Coast do not automatically get the hundred courses. The coordinator within West Coast have to go in there and then manually decide which user within West Coast should take which course. So by setting this to allow, it will become a two-step process for user to get enrolled in a course, whereas

video tutorial

set up affiliates

OASIS platform

administrators

dashboard