Cards: Difference between revisions
Jump to navigation
Jump to search
Telcredstaff (talk | contribs) (→Cards) |
Telcredstaff (talk | contribs) |
||
| (20 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Cards refers to both actual cards and keyfobs. |
|||
Telcred currently supports two main types of devices or credentials: cards and mobile phones. |
|||
== |
== Adding a card == |
||
Cards can be added in three different ways: |
|||
| ⚫ | |||
# 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. |
|||
| ⚫ | |||
== Card fields == |
|||
[[File:add_card.png|Add card]] |
|||
The fields for a card are: |
|||
* ''Name''. The only mandatory field |
|||
* ''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 |
||
* ''Card ID''. The ID of the card in either hexadecimal or decimal notation (see above) |
|||
| ⚫ | |||
* ''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 |
|||
At the bottom of the page, there is a link that lets you [[Validating access|check the access rights for the card]]. |
|||
[[File:create_card.png|Create card]] |
|||
When adding a new card it is required to give it a name. It is also possible to enter an optional description. |
|||
| ⚫ | |||
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 swipe 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 be temporarily blocked, e.g. if it is lost. If found again, the card can simply be unblocked. |
|||
| ⚫ | |||
== Mobile phones == |
|||
To register a mobile phone, add a new ''Device'' and select type ''Mobile phone''. |
|||
[[File:create_phone.png|Create phone]] |
|||
Just like for cards, it is possible assign the phone to a user, specify the time period during which the phone should be active, and to block it temporarily if it has been lost. |
|||
After saving, a ''Registration code'' is presented which is needed when starting the [[Telcred_Entry|Telcred Entry]] app for the first time. This associates the app that the user downloaded and installed with its corresponding identity in Telcred Access Manager. After the user has entered this code in the app, its ''Registered'' status will change to ''yes''. |
|||
[[File:reg_code.png|Registration code]] |
|||
Latest revision as of 10:00, 10 April 2023
Cards refers to both actual cards and keyfobs.
Adding a card
Cards can be added in three different ways:
- 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
The fields for a card are:
- Name. The only mandatory field
- 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
- 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 Users screen.
- 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
At the bottom of the page, there is a link that lets you check the access rights for the card.