Tabs - Revision history

Telcredstaff: /* Controllers */

2019-07-04T16:33:21Z

Controllers

← Older revision		Revision as of 16:33, 4 July 2019
Line 119:		Line 119:
	Typically, the controller settings will be done by the installer / integrator and not by the end customer administrator.		Typically, the controller settings will be done by the installer / integrator and not by the end customer administrator.

	More information about controllers can be found [[~~A1001_settings~~\|here]].		More information about controllers can be found [[Controllers\|here]].

	== Hubs ==		== Hubs ==

Telcredstaff: /* Hubs */

2018-11-01T13:40:02Z

Hubs

← Older revision		Revision as of 13:40, 1 November 2018
Line 123:		Line 123:
	== Hubs ==		== Hubs ==

	Hubs are only used in connection with wireless locks from [[Assa Aperio]]. Before a hub can be linked to a controller, it needs to be created here.		Hubs are only used in connection with wireless locks from [[SimonsVoss SmartIntego]] or [[Assa Aperio]]. Before a hub can be linked to a controller, it needs to be created here.

	More information about hubs can be found [[Hubs\|here]].		More information about hubs can be found [[Hubs\|here]].

Telcredstaff: /* Start */

2018-08-02T13:02:39Z

Start

← Older revision		Revision as of 13:02, 2 August 2018
Line 5:		Line 5:
	* Latest events		* Latest events
	* Offline doors		* Offline doors
	* Statistics on number of doors, users, devices, etc.		* Statistics on number of doors, users, devices, etc.

Telcredstaff: /* Notifications */

2018-08-02T12:31:14Z

Notifications

← Older revision		Revision as of 12:31, 2 August 2018
Line 64:		Line 64:
	== Notifications ==		== Notifications ==

	An administrator can setup a ''Notification'' in order to get an email, an SMS, or both, when certain events occur.		An administrator can setup a ''Notification'' in order to get an email, an SMS, or both, when certain events occur. It is possible to specify which types of events that should trigger a notification, and also when notifications should be generated (e.g. only outside office hours).

			More information about notifications can be found [[Notifications\|here]].

	== Policies ==		== Policies ==

Telcredstaff: /* Events */

2018-08-02T12:26:20Z

Events

← Older revision		Revision as of 12:26, 2 August 2018
Line 61:		Line 61:

	More information about events can be found [[Events\|here]].		More information about events can be found [[Events\|here]].

			== Notifications ==

			An administrator can setup a ''Notification'' in order to get an email, an SMS, or both, when certain events occur.

	== Policies ==		== Policies ==

Telcredstaff: /* Doors */

2018-04-11T14:58:33Z

Doors

← Older revision		Revision as of 14:58, 11 April 2018
Line 91:		Line 91:
	== Doors ==		== Doors ==

			The Doors tab is used to change the door settings, e.g. access time, "open too long" alarm, and unlock schedule. It is also possible to check the status of the door (if it is locked and closed) and to perform the following actions:
	There are a few parameters to set when creating a new door:
			* Grant access

			* Manually unlock
	* ''Name''. Should be something meaningful to the administrator (and possibly the end users if they have the ''Telcred Entry'' app)
			* Manually lock
	* ''Description''. Optional
			* Return to schedule
	* ''Access time''. This is the time the lock stays unlocked after a credential has been accepted by the reader
	* ''Open too long alarm''. After this time the alert ''Door left open'' will be generated
	* ''Pre-alarm''. The number of seconds before ''Open too long time'' that the reader will warn the user to close the door
	* ''Unlock''. The door will be unlocked according to a schedule (e.g. weekdays between 09.00 and 17.00). If the door has two locks, both will be unlocked
	* ''Unlock lock 2 only''. Allows to unlock only the second lock according to a schedule (typically a night lock / motor lock)

	More information about doors can be found [[Doors\|here]].		More information about doors can be found [[Doors\|here]].

Telcredstaff: /* Users */

2018-04-11T13:45:17Z

Users

← Older revision		Revision as of 13:45, 11 April 2018
Line 34:		Line 34:
	== Users ==		== Users ==

	Users are the end users of the system that need to be able to open doors. A ~~user~~ ~~must~~ ~~have~~ a ~~name~~.		Users are the end users of the system that need to be able to open doors. Access rights are always set for a user (using either ''Roles'' or ''Assignments'').

	~~Access rights are always set for a user (using either ''Roles'' or ''Assignments'').~~ A user can be the owner of one or more devices. Every device that a user owns, will inherit the access rights of its owner.		A user can be the owner of one or more devices. Every device that a user owns, will inherit the access rights of its owner.

	In addition to the mandatory name, a user can have several optional attributes that can be used to sort and filter users, e.g. Department and Employee ID.		In addition to the mandatory name, a user can have several optional attributes that can be used to sort and filter users, e.g. Department and Employee ID.

Telcredstaff: /* Visits */

2018-04-11T13:29:10Z

Visits

← Older revision		Revision as of 13:29, 11 April 2018
Line 26:		Line 26:
	The purpose of ''Visits'' is to enable people who are not registered users in the system to access one or more doors during a limited time. A typical use case could be an event where you want the guests to be able to let themselves in through the front door, but only on the night of the event.		The purpose of ''Visits'' is to enable people who are not registered users in the system to access one or more doors during a limited time. A typical use case could be an event where you want the guests to be able to let themselves in through the front door, but only on the night of the event.

	When creating a new visit, the system will generate a URL (web address) that can be pasted into an email and sent to the visitors. When the visitor clicks the URL in the email application on their smartphone it takes them to a web page where they will see an "~~Access~~" button for each door included in the visit.		When creating a new visit, the system will generate a URL (web address) that can be pasted into an email and sent to the visitors. When the visitor clicks the URL in the email application on their smartphone it takes them to a web page where they will see an "Open" button for each door included in the visit.

	It should be noted that ''Visits'' is relatively low security because anybody who has access to the URL can open the door, and it is not possible to know the identity of the actual person who did the opening. On the other hand the access buttons are only visible and possible to use during the time of the visit.		It should be noted that ''Visits'' is relatively low security because anybody who has access to the URL can open the door, and it is not possible to know the identity of the actual person who did the opening. On the other hand the access buttons are only visible and possible to use during the time of the visit.

Telcredstaff: /* Hubs */

2018-04-11T10:38:44Z

Hubs

← Older revision		Revision as of 10:38, 11 April 2018
Line 121:		Line 121:
	== Hubs ==		== Hubs ==

			Hubs are only used in connection with wireless locks from [[Assa Aperio]]. Before a hub can be linked to a controller, it needs to be created here.
	''Coming soon''.

	More information about hubs can be found [[Hubs\|here]].		More information about hubs can be found [[Hubs\|here]].

Telcredstaff: /* Controllers */

2018-04-11T10:35:51Z

Controllers

← Older revision		Revision as of 10:35, 11 April 2018
Line 113:		Line 113:
	== Controllers ==		== Controllers ==

			A controller controls one or more doors and has a number of settings related to the door hardware, e.g. the lock configuration, type of reader, if a door monitor or REX-button (REquest to Exit) is used etc. The controller also has settings related to its own time zone, connection mode and firmware.
	The first parameters to set for a new controller are time zone, connection mode, if a hub will be used, and which door(s) are connected to the controller.

			Typically, the controller settings will be done by the installer / integrator and not by the end customer administrator.
	Connection mode can be ''O3C'' or ''direct''. O3C stands for One-Click-Connection-Component and is a technology developed by Axis Communications that allows the door controller to connect to a cloud service in a secure way, without any need for setting up port forwarding and that is accepted by most firewalls. After connecting the reader and other peripherals, the installer pushes a button on the door controller which then contacts first an Axis server to get a certificate, and immediately after that connects to the Telcred service.

	Two numbers are needed for O3C to work: the door controller's serial number and OAK (Owner Authentication Key). The serial number is printed on the door controller itself and the OAK is provided on a piece of paper in the box it is shipped in. If the connection mode is ''direct'', the Telcred service will contact the door controller, as opposed to the other way round. For this connection mode, it is necessary to specify the IP-address and port of the door controller (and it is also necessary to configure the local firewall or router to allow this traffic to pass through).

	A ''hub'' refers to a device necessary to communicate with Assa Aperio wireless locks. If Assa Aperio is not part of the installation, no hub should be configured.

	The door(s) connected to the controller are created using the ''Doors'' tab. In other words, it makes sense to create the door first before setting up the controller.

	Then there are a number of settings that have to do with the peripherals connected to the door controller:

	* Door monitor
	* Lock configuration and behaviour if power is lost (fail secure or fail safe)
	* Reader(s)
	* REX-button(s) (Request to EXit)

	More information about controllers can be found [[A1001_settings\|here]].		More information about controllers can be found [[A1001_settings\|here]].