Cards - Revision history

Telcredstaff: /* Adding a card */

2023-04-10T10:00:09Z

Adding a card

← Older revision		Revision as of 10:00, 10 April 2023
Line 3:		Line 3:
	== Adding a card ==		== Adding a card ==

			Cards can be added in three different ways:
⚫	A ~~common~~ ~~way to add a new~~ card ~~to the system is to first touch it to~~ a connected reader. Then select [[Events]] in the Monitoring section of the menu. An unknown ~~device~~ should appear at the top of the list with a link to add it (it can take a few seconds before the event shows up). Click the link to add the information for the new card.

			# In Card Management (part of [[Site Manager]]) ranges of cards can be generated. This is a great option if the Site includes a large number of cards/key-fobs.
			#* From Card Management, cards can be allocated to Tenant Systems.
			# Press "Add new" under Cards in Access Manager and fill in the details.
			#* Card ID must be known and supplied.
			# Trough a connected reader.
		⚫	#* Swipe the card/key-fob on a connected reader. Then select [[Events]] in the Monitoring section of the menu. An unknown card should appear at the top of the list with a link to add it (it can take a few seconds before the event shows up). Click the link to add the information for the new card.

	== Card fields ==		== Card fields ==

Admin: /* Card fields */

2022-12-14T20:12:49Z

Card fields

← Older revision		Revision as of 20:12, 14 December 2022
Line 12:		Line 12:
	* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead		* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead
	* ''Card ID''. The ID of the card in either hexadecimal or decimal notation (see above)		* ''Card ID''. The ID of the card in either hexadecimal or decimal notation (see above)
	* ''User''. A card can only belong to one user at the time, but it is possible to reassign it from one user to another. The card can be assigned to a user in this screen or it can be done in the [[~~User~~]] screen.		* ''User''. A card can only belong to one user at the time, but it is possible to reassign it from one user to another. The card can be assigned to a user in this screen or it can be done in the [[Users]] screen.
	* ''Active''. It is possible to set a date range for when the card should be active		* ''Active''. It is possible to set a date range for when the card should be active
	* ''Blocked''. A card which has been lost can be blocked. In this case it will not be able to open doors. If the card is found again it can simply be unblocked		* ''Blocked''. A card which has been lost can be blocked. In this case it will not be able to open doors. If the card is found again it can simply be unblocked

Admin: /* Card fields */

2022-12-14T20:11:56Z

Card fields

← Older revision		Revision as of 20:11, 14 December 2022
Line 11:		Line 11:
	* ''Notes''. Optional and for information only		* ''Notes''. Optional and for information only
	* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead		* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead
	* ''Card ID''. The ID of the card as ~~sent~~ by ~~the~~ ~~card~~ ~~reader~~		* ''Card ID''. The ID of the card in either hexadecimal or decimal notation (see above)
	* ''User''. A card can only belong to one user at the time, but it is possible to reassign it from one user to another. The card can be assigned to a user in this screen or it can be done in the [[User]] screen.		* ''User''. A card can only belong to one user at the time, but it is possible to reassign it from one user to another. The card can be assigned to a user in this screen or it can be done in the [[User]] screen.
	* ''Active''. It is possible to set a date range for when the card should be active		* ''Active''. It is possible to set a date range for when the card should be active

Admin: /* Card fields */

2022-12-14T20:10:40Z

Card fields

← Older revision		Revision as of 20:10, 14 December 2022
Line 6:		Line 6:

	== Card fields ==		== Card fields ==
	A card can only belong to one user at the time, but it is possible to reassign it from one user to another.

	The fields for a card are:		The fields for a card are:

Line 14:		Line 12:
	* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead		* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead
	* ''Card ID''. The ID of the card as sent by the card reader		* ''Card ID''. The ID of the card as sent by the card reader
	* ''User''. ~~The~~ ~~owner~~ of the ~~card~~. The card can be assigned to a user in this screen or it can be done in the [[User]] screen.		* ''User''. A card can only belong to one user at the time, but it is possible to reassign it from one user to another. The card can be assigned to a user in this screen or it can be done in the [[User]] screen.
	* ''Active''. It is possible to set a date range for when the card should be active		* ''Active''. It is possible to set a date range for when the card should be active
	* ''Blocked''. A card which has been lost can be blocked. In this case it will not be able to open doors. If the card is found again it can simply be unblocked		* ''Blocked''. A card which has been lost can be blocked. In this case it will not be able to open doors. If the card is found again it can simply be unblocked

Admin: /* Card fields */

2022-12-14T20:09:51Z

Card fields

← Older revision		Revision as of 20:09, 14 December 2022
Line 6:		Line 6:

	== Card fields ==		== Card fields ==

	If, instead, the card should be identified by ''Number'', the ''Card ID'' should be entered as a decimal number (e.g. 12408).

	In general, it is always better to use ''Raw bits'' and the only reason to use ''Number'' is for backwards compatibility with a previous access control system (for example, if the customer already has a large number of cards for which only the decimal number is known, and it is not practical to collect and re-register the cards).

	The card can be assigned to a user in this screen or it can be done in the ''User'' screen. It is possible to specify the time period during which the card should be active. A card which does not belong to a user or is no longer active is not able to open any doors.


	A card can only belong to one user at the time, but it is possible to reassign it from one user to another.		A card can only belong to one user at the time, but it is possible to reassign it from one user to another.

Line 22:		Line 14:
	* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead		* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead
	* ''Card ID''. The ID of the card as sent by the card reader		* ''Card ID''. The ID of the card as sent by the card reader
	* ''User''. The owner of the card		* ''User''. The owner of the card. The card can be assigned to a user in this screen or it can be done in the [[User]] screen.
	* ''Active''. It is possible to set a date range for when the card should be active		* ''Active''. It is possible to set a date range for when the card should be active
	* ''Blocked''. A card which has been lost can be blocked. In this case it will not be able to open doors. If the card is found again it can simply be unblocked		* ''Blocked''. A card which has been lost can be blocked. In this case it will not be able to open doors. If the card is found again it can simply be unblocked

Admin: /* Card fields */

2022-12-14T20:07:41Z

Card fields

← Older revision		Revision as of 20:07, 14 December 2022
Line 20:		Line 20:
	* ''Name''. The only mandatory field		* ''Name''. The only mandatory field
	* ''Notes''. Optional and for information only		* ''Notes''. Optional and for information only
	* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the ~~card~~ ~~registration~~ ~~process~~ above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead		* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the process for adding a card above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead
	* ''Card ID''. The ID of the card as sent by the card reader		* ''Card ID''. The ID of the card as sent by the card reader
	* ''User''. The owner of the card		* ''User''. The owner of the card

Admin: /* Card fields */

2022-12-14T20:06:54Z

Card fields

← Older revision		Revision as of 20:06, 14 December 2022
Line 20:		Line 20:
	* ''Name''. The only mandatory field		* ''Name''. The only mandatory field
	* ''Notes''. Optional and for information only		* ''Notes''. Optional and for information only
	* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If ~~raw~~ bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the card registration process above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead		* ''Identified by''. Can be 'Raw bits' or 'Number'. Raw bits is the default and means that the card is identified by all the bits that the reader receives from the card. If Raw bits is chosen, the ''Card ID'' needs to be entered with hexadecimal notation (this is done automatically if the card registration process above is followed). We recommend to always use Raw bits, which is exactly what the card reader sends to the controller. If the reader model does some pre-processing of the card identity, it can sometimes work to use 'Number' instead
	* ''Card ID''. The ID of the card as sent by the card reader		* ''Card ID''. The ID of the card as sent by the card reader
	* ''User''. The owner of the card		* ''User''. The owner of the card

Admin at 20:05, 14 December 2022

2022-12-14T20:05:49Z

← Older revision		Revision as of 20:05, 14 December 2022
Line 13:		Line 13:
	The card can be assigned to a user in this screen or it can be done in the ''User'' screen. It is possible to specify the time period during which the card should be active. A card which does not belong to a user or is no longer active is not able to open any doors.		The card can be assigned to a user in this screen or it can be done in the ''User'' screen. It is possible to specify the time period during which the card should be active. A card which does not belong to a user or is no longer active is not able to open any doors.

	A card can be temporarily blocked, e.g. if it is lost. If found again, the card can simply be unblocked.

	A card can only belong to one user at the time, but it is possible to reassign it from one user to another.		A card can only belong to one user at the time, but it is possible to reassign it from one user to another.
Line 25:		Line 24:
	* ''User''. The owner of the card		* ''User''. The owner of the card
	* ''Active''. It is possible to set a date range for when the card should be active		* ''Active''. It is possible to set a date range for when the card should be active
	* ''Blocked''. A card which has been lost can be blocked. In this case it will ~~noty~~ be able to open doors. If the card is found again it can be unblocked		* ''Blocked''. A card which has been lost can be blocked. In this case it will not be able to open doors. If the card is found again it can simply be unblocked


	At the bottom of the page, there is a link that lets you [[Validating access\|check the access rights for the card]].		At the bottom of the page, there is a link that lets you [[Validating access\|check the access rights for the card]].

Admin: /* Adding a card */

2022-12-14T20:04:33Z

Adding a card

← Older revision		Revision as of 20:04, 14 December 2022
Line 3:		Line 3:
	== Adding a card ==		== Adding a card ==

	A common way to add a new card to the system is to first touch it to a connected reader. Then select ''Events'' in the Monitoring section of the menu. An unknown device should appear at the top of the list with a link to add it (it can take a few seconds before the event shows up). Click the link to add the information for the new card.		A common way to add a new card to the system is to first touch it to a connected reader. Then select [[Events]] in the Monitoring section of the menu. An unknown device should appear at the top of the list with a link to add it (it can take a few seconds before the event shows up). Click the link to add the information for the new card.


	== Card fields ==		== Card fields ==

Admin at 20:04, 14 December 2022

2022-12-14T20:04:08Z

@@ Line 5: / Line 5: @@
 A common way to add a new card to the system is to first touch it to a connected reader. Then select ''Events'' in the Monitoring section of the menu. An unknown device should appear at the top of the list with a link to add it (it can take a few seconds before the event shows up). Click the link to add the information for the new card.
 If, instead, the card should be identified by ''Number'', the ''Card ID'' should be entered as a decimal number (e.g. 12408).
@@ Line 28: / Line 29: @@
 At the bottom of the page, there is a link that lets you [[Validating access|check the access rights for the card]].