EventKeeper has different levels of responsibility for different logins. In the simplest terms, ADMIN logins can add and edit everything including events and global changes. Team logins can add and edit events that belong to their teams. Those exist on opposite ends of the spectrum with a couple other designations in between. Below is a list of login types starting with the most responsibility and ending with the least.
ADMIN login -
This is for calendar admins who are in charge of the look, set up, and functionality of the calendar. This login has the word ADMIN in the team field. Admins can:
JRADMIN-
This login can do almost everything an ADMIN can do almost everything that an ADMIN can do except access the ADMIN page to edit global settings. This login cannot approve patron room requests in EKRooms. This login has JRADMIN in the team field. JRADMINS can:
TEAM login -
This login is for general users of EventKeeper and allows the user to add, edit, and delete events associated with their team. For example, events made by logins with the REFERENCE team can only be edited by other logins that are on the same REFERENCE team or ADMINS and JRADMINS. A login with the CIRC team could not touch that event made by REFERENCE. When making a team login, simply type in the name of the team you want to create in the TEAM field when creating an editor. A team can be called whatever you like. Many libraries have teams like REF, CIRC, CHILDRENS, etc. TEAM logins can:
TEAM*
This login is just like the TEAM logins, but cannot see pending events. To create this login, add an * after the team name ie KN-REFERENCE*. TEAM* logins can:
View Only
This login allows the user to see events that are typically hidden from the public, such as events that are marked at BUSY. It has no editing abilities. It can be part of any team. On the editor creation page, fill in whatever team you like, but set the Editor Post Status as VIEW (NO-POSTING). If VIEW (NO-POSTING) doesn't show up as an option when you are making a new editor, go into ORG INFO and toggle YES to Private Events. Then VIEW will show up.
* View only logins can also see class lists in EKReg.
Patron Request (Room Matrix)
This login is used for patrons when they create their event or room requests. This login happens automatically when a patron clicks on the "Request a Room" or "Request and Event" links. It can only submit a request and cannot edit anything.
EventKeeper has different levels of responsibility for different logins. In the simplest terms, ADMIN logins can add and edit everything including events and global changes. Team logins can add and edit events that belong to their teams. Those exist on opposite ends of the spectrum with a couple other designations in between. Below is a list of login types starting with the most responsibility and ending with the least.
ADMIN login -
This is for calendar admins who are in charge of the look, set up, and functionality of the calendar. This login has the word ADMIN in the team field. Admins can:
JRADMIN-
This login can do almost everything an ADMIN can do almost everything that an ADMIN can do except access the ADMIN page to edit global settings. This login cannot approve patron room requests in EKRooms. This login has JRADMIN in the team field. JRADMINS can:
TEAM login -
This login is for general users of EventKeeper and allows the user to add, edit, and delete events associated with their team. For example, events made by logins with the REFERENCE team can only be edited by other logins that are on the same REFERENCE team or ADMINS and JRADMINS. A login with the CIRC team could not touch that event made by REFERENCE. When making a team login, simply type in the name of the team you want to create in the TEAM field when creating an editor. A team can be called whatever you like. Many libraries have teams like REF, CIRC, CHILDRENS, etc. TEAM logins can:
TEAM*
This login is just like the TEAM logins, but cannot see pending events. To create this login, add an * after the team name ie KN-REFERENCE*. TEAM* logins can:
View Only
This login allows the user to see events that are typically hidden from the public, such as events that are marked at BUSY. It has no editing abilities. It can be part of any team. On the editor creation page, fill in whatever team you like, but set the Editor Post Status as VIEW (NO-POSTING). If VIEW (NO-POSTING) doesn't show up as an option when you are making a new editor, go into ORG INFO and toggle YES to Private Events. Then VIEW will show up.
* View only logins can also see class lists in EKReg.
Patron Request (Room Matrix)
This login is used for patrons when they create their event or room requests. This login happens automatically when a patron clicks on the "Request a Room" or "Request and Event" links. It can only submit a request and cannot edit anything.