In almost all cases, when you have an account in OASIS, we actually track the most relevant information, such as name, email, and the user's member ID with your AMS or CRM. Occasionally, you might say, I need additional fields. Obviously, OASIS cannot be designed to accommodate every possible field that every single client uses OASIS will ever need, because that's not quite scalable. To answer that question, what OASIS does is we have this feature called Custom Fields. When you click on it, you will see that OASIS allows administrator to extend other fields that you would like to track for each user. In this particular case, I'm tracking the profession that comes from single sign-on. Let's not worry about where the data come from for now. Let's just focus on what is the purpose of having this field. By default, if your system doesn't have this field, when you come here, it will be empty. In my example here, I have one field already. Once I do that, anytime you need to download a report. For example, let's say I want to download everybody who has logged in the last 30 days. When I export, you will see that this field is part of the column that's available to me. When I download this data, obviously I need to go to a queue. I will just quickly show that the idea behind Custom Fields for a user account is so that this particular field is always part of any report that contains a user. The benefit of having such Custom Fields in your system is so that you can have additional information about the user that might be relevant for reporting purpose. You can always rely on the fact that they will be part of the export from OASIS as long as you have put a value next to these fields in OASIS. In the next field tutorial, we'll talk about how to leverage these fields. Thank you.

OASIS

Custom Fields

user data

reports

data accuracy