This video walkthrough will show how to set up a document repository that allows user-generated content. The basic workflow for user-generated content is the user first upload the document, one or more, which are in an initial state that is invisible to the general public. A email notification will be sent to any designated email address, and you can have admin or faculty to approve or reject the uploaded content. Lastly, when the document has been approved, administrator can make the document visible. Note that the approval or reject of the uploaded document can be done by admin or faculty. The idea here is, if the subject matter expert is a faculty, you want the faculty to approve or reject, but admin is in charge of the final step, which is to make any approved document visible. With that said, in this quick walkthrough, we're just going to use four actors. We have administrator, Benjamin, we have a faculty, John, and we have two users, Lisa and Aaron. We're just going to quickly go through how that works. In the back, we have Benjamin logging in as administrator, and we have a document repository called Submit Your Content, or Abstract. There's a couple of things I want to highlight. Under Manage Features, Allow User Upload is checked. This opens up the capability for user to upload content, whereas a typical course administrator or the faculty is the one that loads content into the course. With that said, a couple of things that I want to highlight before we start the demo. The first is, we have configured John Day as a faculty for this particular course. You can obviously add additional faculties to the course. Any faculties will have the ability to approve or reject a particular course, a particular content. This is in addition to administrators who have full access. In addition, there is an email address called Content Update Notification. This email is going to be sent any time there is any content uploaded. For example, you can say, I want an email address called Notification at 360factor.com, which is going to receive an email any time someone uploads, approves, or rejects a content. You could put John Day's email in here, so that the faculty, John Day, will be able to get notified when someone uploads. You can also put one or two administrators' email in here. The idea is that we decouple who has authorization to approve or reject from who received the email, so that you can manipulate the workflow that's most suitable for your organization. Now that we have shown the setup, currently there isn't any course loaded, so we're just going to log in as one of the users and start the trigger, the workflow process. We have logged in as Lisa, which is one of the users, and we're going to go to Library, where this particular course is located, and we're going to click on Access. Now before the user does anything, we can see that there isn't anything loaded here, so we click on Upload, and we're just going to select a few documents. To make it simple, we're just going to select some PDF files, so that they can be seen quickly. So this is the same UI that the administrator uses to create documents, to upload the document. As you can see here right away, they are listed under Pending Approval, and the user, general public, don't see anything. Only the person who uploaded the content will see the content that they have uploaded. And then, they can also make some basic comments, like, this is the research I was working on last year. So they can make simple comments in here. Note that these comments are not displayed to the general public. So now that it has been uploaded, we then can switch over to the administrator to show what the administrator can see. So we're just going to switch to... So we're going to refresh the screen. And you can see here, the three documents that have been uploaded are displayed here, and the comment that the user made is right here. So we can actually make another comment, to say, I will check with John Day and see if this is good. So as you can see, there is some limited commenting functionality going back and forth. In addition, if we go to Email Notification, we'll see who has been notified throughout this workflow for user-generated content. So here we go. You can see that when content has been uploaded, this email is notified. So now, let's switch over to a faculty role, who is John Day, and let's see what John Day sees. So let's go to My Courses, and this is the course that he's in charge of. And here is the three pieces of content that's available. So John Day can also make a comment, say, this is great. And then, John Day can approve it. John Day can approve another one, unless they reject another one. And let's say here, I'm just going to make a comment, say, I am rejecting it, because it is a repeat, for example, of last year's submission. Here we go. As the faculty make these approvals and rejections, approve, approve, reject, the system is actually sending out notifications so that the person who submitted it will know that their submission has either been approved or rejected. And notice that the notification is also being cc'd. Now, if I switch over to Lisa's account, and I'm just going to refresh the screen, you'll see that approved and rejected is listed. But the general public still have not seen this. The reason they haven't seen it is because Administrator has not approved it. So we're going to switch over to Administrator, and we're just going to quickly jump over and make them visible. So when Administrator goes in, under Content, they will see that this is approved, this is approved, this is rejected, and these are still hidden. So I can click on the eye icon to turn it visible. Now if I switch over to Lisa's account, the two out of the three is visible now. We can further approve this by logging in as the second user, Aaron. Now we have logged in as Aaron. We can actually access the same course and see the two things that has been made visible after they were approved. And Aaron can also add a few content. So let's add another content. And notice these also have its own approval, and general public don't see it. And as a quick demonstration, we're just going to quickly approve these as Administrator instead of waiting for the faculty. So I'm going to approve it, and I'm going to make it visible. Now as when Aaron logs in, this is Aaron, you'll see that everything has been made visible to everybody. So this is just a quick run through of how someone can upload a content, receive approval or rejection, and for all the approved ones, you can make them visible as the last step.

document repository

user-generated content

uploading documents

email notifications

approval process