• Roles are a combination of different permissions that we have set to define different levels of usage. Each user who has access to the Vidigami system needs to have a Role associated with him/her. We have 5 roles that define what they can/can not do in the system. They are as follows:
  1. Administrator:

    • This the most powerful role in the school (if this is set at a system-wide level).
    • Every school needs to have at least one school administrator per school year. We receive the details of that one user from the school when onboarding to create the account (and to launch). This person will be managing users/content etc. This is a system-wide permission that will grant control over all Groups and all content in that school year.
    • Every year the school admin can be different.
    • Over time, the school admin may choose to add a new user also as “school admin.” To do that, the current school admin can go to the Enrollments page and update the role of that particular user to “admin.” This will affect the permission of that user allowing them to gain control over all Group and its content in that school year.
    • A user can also be an “Admin” of a Group. To make a user an admin of a particular group, he/she has to be a member (except if the user is already a system-wide admin). The Group admin can manage the content/users but only for that Group.
  2. Manager

    • This role is almost as powerful as the admin. This can be limited to certain Groups or be a system-wide role for the user. The manager can do everything the admin can aside from managing users (Enrollments), managing Flagged photos and managing Tags (from the Tag management section).
  3. Contributor

    • This role is mainly for users to be able to contribute photos to the system and can be limited to certain Groups or be a system-wide role for the user.
  4. Spectator

    • The users with this role are provided with the permission to only view photos and limited access to download photos in the application. Their access can be limited to certain Groups or be a system-wide role for the user.
  5. No Access

    • To give users very limited to no access to the system, the school can choose this role to only allow the user to have access to only certain parts of the system.
  6. Custom Roles


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.