 Good morning, sir. Good morning, sir. And good morning. And our model is role management. Actually, the motivation behind implementing this role management means, in our TQ model, the one which we are using this software, there are many roles, like RCC, WCC, and participant admin and principal delivery manager, principal course manager. These many fields are there. Actually, while coming to the normal software, there will be only two users, normally, user and admin. And while coming to admin, suppose when a person log-ins, if you want to show the admin panel or according to that, if you want to show user panel, we will hard-code the values, like if user ID is this one, show admin panel. If it fails, we will show user panel. That is the normal thing which will happen in this one. But in that role management, which is a dynamic one, we will give role-based permission to all the pages which are existing in the software. When a person log-ins, we will get the role ID. And suppose if a user can extend from, suppose if a participant is already attended, he can be promoted to another role, like assistant faculty. So, based on that, it will be a dynamic thing. That's why we implement this role management. And while coming to the role management, here, when in the dashboard, there are only five views. But that is roles, modules, pages, tags, and modify-axing roles. While coming to the roles, I want to show the live demo. And this role management has high authority to power over all the softwares. See, this is our dashboard. And while coming to the roles, these are the current roles which are existing in the software. There are 10 roles, like a normal user business and all these things. And if you want any new role, you can add those. And we created another feature in that that you can deactivate one particular role from axing this complete software. And you can make them active. This is one feature. And while coming to the modules... Let me ask few questions over here. Now, if I have to create one role, the role will be given certain rights. The role is basically defined by the rights. So, where are the rights? I will come in the axing roles while coming to the last one. You show the role, you show the rights. You show the combination of the rights and that makes the role. Otherwise, role is a label for me. Actually, the combination means, here the combination is roles and modules. We have to make them combination. So, first I will explain roles, then modules, then I will explain the combination of them. That is the flow. Actually, that's why I am going. Okay, okay. Continue. These are the modules which they are working. Like, attendance module, certificate module, course creation module, all these things are they are working. And in the pages, for every particular module, they have separate individual pages. These are the things. Unlike tags only. For a particular tag, there are individual tags. And this is the one which is a dynamic one, axing roles. This is the main part of this role management. Here, it will show all the list of the modules which are existing in that. While going into that, a particular module, it will show the list of the pages in that attendance module, which is a dynamic one. And here, going to the last one here, this is the roles accessible to this module. Here, you can delete this one or you can add any role who can access this one. What do you mean by dynamic? Suppose in that attendance module, there will be a button, update attendance button will be there. This can be presently the participant who is attending the workshop. He can only view that button that particular day. Suppose in the previous day, he cannot modify the attendance in the previous day. But while coming to the RCC, who is conducting that workshop, he can also be visible to see in that day only. He cannot see the previous one. While coming to the admin, he has the complete privileges to access any date and anything. You mean the visibility is time-restricted, correct? Role-based restricted. You are saying time. Yesterday, today, that is what I am saying there. It is time-restricted? No, there we use it. The time is today under role-based also, sir. Okay, okay, continue. The session is expiring? No, no, sir. Actually, I am using in this incognito mode. Why the port number is 9000? For our tester, we are normally using 9000. We can use 8000 or anything. Why somebody has to put a port number? Why should not it go as a normal HTTP? Actually, it is a test server, sir. While testing, we have created 9000. Otherwise, we can directly host in the website and with the port 8-0. Just normally, for the test server, we are using 9000. While running the server, we can port 8-0 also. I don't know. Okay, okay, sir. Actually, I logged in as participant. When a person log-ins, he can apply for a feedback form. We will be there, sir. In the feedback form, a participant can only see the feedback form. In the role-based one, faculty pool feedback. Here, I am showing that the role is accessible only for normal user. Now, I am dealing with that user. Now, nobody can access this page. Now, I am going to this. See, the page is automatically redirected back. He can access that page. That is fine. The basic questions are whether you can add on the roles. Can I have two roles? Yes, sir. See, new page role. I am again adding participant feedback. Normal user can access a new page role. Participant feedback page. And he can also... Principal course delivery manager can also add. No, no, no. You are adding the access to the pages to me. Right? What I am saying is that I have got two roles. For example, your remote center controller is one role with certain kind of rights. Your participant is some role having some rights. Now, can I have two roles? No, no. No. But it is many times needed. Do you say that Dr. Fartuck cannot attend any course given by this? It is needed many times. Sir, then... No, no. Give me the simple question. Dr. Fartuck is a faculty. Can he attend a course or not? Yes, sir. How? This can be solved by this role management. No, no, no. There should be a provision that you can have multiple roles. For example, suppose somebody is doing some job and his assistant or somebody else goes on leave. He has to give the charge to some other person for limited time. So he should have an add-on role. Somebody is a cameraman and somebody has got some other jobs to do. But that fellow has gone out for some time. He has given his responsibility to him. So he should have the access to all the rights what he have. Sir, let me explain. So there should be the possibility of having multiple roles in any role management system. Let me explain in this view, sir. Suppose that person has to access this cameraman. In that particular time, I will give this camera access to that person. No, no, no. That is not allowed. You can't do that because you want to give that access only to him. Not to everybody. No other cameraman. Then I will create a new role in that system. Not possible. How come your role management work? That for every case, you have to create one role. There should be the possibility that you can add on the role. That is not available. Actually, in that our test server, there is for a particular role. No, no. I mean, I cannot attend any course because she has got, I mean, rights. Actually, in the database, try to accept some things. There is a mandatory field which is with the good role management system that you can have add on roles. Okay. If it is not available, say it is not available, you will develop. Okay. Don't argue unnecessarily. Thank you. Second thing, whenever you are controlling roles, you are showing me the list of pages. While restricting how exactly you are doing the work, whether you are hiding the things and showing the things or you are actually controlling the access. Actually, I am controlling the things. Actually, when the... He is hiding. He is hiding. So, hiding... Good hiding example. That is what I am saying. Hiding is not the basic trick by which people were doing it from ages. But it is not the basic technique by which the role management can be done. Whether you are using any MVC architecture? It is not hiding, sir. Actually, let me explain. Here the thing is making inactive means I am just showing their names here. While coming to the page, before the rendering the page itself, it will check the ID with the user ID and then only it will enter the page. Otherwise, it will redirect to homepage itself. You are using MVC architecture? No, no, sir. In the view... See it. Do you know? So, whether you are controlling the view at the level of controller, what I am saying that this is visualization. So, in MVC architecture, if the view is being controlled at the controller level, not allowed to pass ahead, then it is a secure way. Otherwise, hide and seek is not allowed. We are using that is the one. So, you have intercepted the interview. Before the loading itself, we achieved. There is an intercept. They don't know. MVC and other thing, they don't know. Okay. The architecture was given to them. The design was given to them. You gave them the design. Record. Okay, continue. I will hand over the session to Pooja. The email content module basically has all the templates which is used by admin and sent to the users. If the users face several issues like change password, edit profile and all, the admin uses these templates and sends it to them. The admin can upload only the HTML files. He is not able to upload any other files. The download link is there. He can even change the template, upload button is there and submit. The template will be automatically changed. This is the download thing. Whether you have referred any standard mailing template-based solutions available in the market, very popular. I think that MonkeyChamp or ChamMonkey. MonkeyChamp. What exactly have you done then? You have just created a file and just push it into the SMTP server. That's all. Actually, according to the users need to do several things. Dispatch, slip, forgot password and all. They are just sent a mail. These mail templates are over there. The admin can use them. This is auto reply kind of thing. Event. Event driven auto reply. Okay. While coming to my another module, this is assistant faculty pooling. The faculty who has cleared an instance of a workshop, who has already cleared an instance, he can desire a wish to apply for an assistant faculty position in that workshop. Actually, the participant who has cleared that workshop, he can be an assistant faculty. He can be a monitor in that workshop. That is the one he can apply for in this interface. When a person login, he can apply for this one. Like he will show the selection criteria. There will be a selection criteria for each workshop by seeing that he can apply. And while coming to the principal faculty, principal faculty take this role to accept or reject that particular assistant faculty based on his grades in that course which he has cleared. And here we are showing those grades fetching from ID bomb X. And based on his feedback also, he can do accept or reject. While if the participant has become assistant faculty, if he approved, then he can go into the assistant faculty for that workshop. After the workshop is conducting, we will take feedback from the participant on that particular assistant faculty based on that feedback, he can remove in the future also. This is the thing we have done in assistant faculty. Page management basically consists of a file, globals.data. It has dictionary, key value pairs. Like in HTML pages we hardcore the things, not title and all. So we don't need to do it anymore. We can use this file and in front of the corresponding key, we can give the title and update it on the HTML page. It will get updated. It is done dynamically.