Privileges - Revision history

Telcredstaff at 11:11, 11 October 2024

2024-10-11T11:11:03Z

← Older revision		Revision as of 11:11, 11 October 2024
Line 1:		Line 1:
	In Telcred Access Manager, privileges express access rights. You can think of a privilege as a key that opens one or more doors with a specified ~~credential~~ (e.g. card + PIN), optionally restricted to times defined by a [[Schedules\|schedule]].		In Telcred Access Manager, privileges express access rights. You can think of a privilege as a key that opens one or more doors with one or more specified credentials (e.g. mobile and card + PIN), optionally restricted to times defined by a [[Schedules\|schedule]].

	The possible credentials are:		The possible credentials are:
Line 16:		Line 16:

	To create a new privilege, select ''Privileges'' in the main menu and click ''Add new''.		To create a new privilege, select ''Privileges'' in the main menu and click ''Add new''.


	[[File:create-privilege.png\|border\|Create privilege]]


Line 25:		Line 22:
	The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]] and is further explained [[SmartIntego settings\|here]].		The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]] and is further explained [[SmartIntego settings\|here]].

	Select which ~~credential~~ should be used. For privileges of type ''Use whitelist where possible'' the only credential type available is ''card only''.		Select which credentials should be used. For privileges of type ''Use whitelist where possible'' the only credential type available is ''card only''.

	''Active'' can be either ''Always'' or ''Only during...'' (specified by a schedule). For privileges of type ''Use whitelist where possible'' it is not possible to specify a schedule.		''Active'' can be either ''Always'' or ''Only during...'' (specified by a schedule). For privileges of type ''Use whitelist where possible'' it is not possible to specify a schedule.

	Finally, select the door(s) the privilege should be able to open ~~by selecting them in the list to the right and moving them over to the left by clicking the left arrow~~. It is possible to specify the doors that the privilege should open either by including the individual [[Doors\|doors]] or one or more [[Door groups\|door groups]]. It is perfectly fine to mix individual doors and door groups in the same privilege.		Finally, select the door(s) the privilege should be able to open. It is possible to specify the doors that the privilege should open either by including the individual [[Doors\|doors]] or one or more [[Door groups\|door groups]]. It is perfectly fine to mix individual doors and door groups in the same privilege.

Telcredstaff at 13:06, 17 January 2024

2024-01-17T13:06:03Z

← Older revision		Revision as of 13:06, 17 January 2024
Line 11:		Line 11:
	* API 2		* API 2

	Mobile remote, Mobile on site, and Mobile at door all concern the [[Telcred_Personal\|Telcred Personal]] mobile app. Mobile remote allows the user to open from anywhere. Mobile on site allows the user to remote open doors when the user is on site. This is determined by comparing the phone's current GPS position with the coordinates for the site defined in [Site Manager]. Mobile at door allows the user to open a door by scanning an NFC tag at the door.		Mobile remote, Mobile on site, and Mobile at door all concern the [[Telcred_Personal\|Telcred Personal]] mobile app. Mobile remote allows the user to open from anywhere. Mobile on site allows the user to remote open doors when the user is on site. This is determined by comparing the phone's current GPS position with the coordinates for the site defined in [[Site Manager]]. Mobile at door allows the user to open a door by scanning an NFC tag at the door.

	The purpose of API 1 and API 2 are to let an external system request access by supplying the door identity and a credential identifier that could represent e.g. a license plate, a face, or the customer's own smartphone app.		The purpose of API 1 and API 2 are to let an external system request access by supplying the door identity and a credential identifier that could represent e.g. a license plate, a face, or the customer's own smartphone app.

Telcredstaff at 13:05, 17 January 2024

2024-01-17T13:05:21Z

← Older revision		Revision as of 13:05, 17 January 2024
Line 5:		Line 5:
	* Card + PIN		* Card + PIN
	* PIN only		* PIN only
			* Mobile remote
	* Mobile remote (Open with the [[Telcred_Personal\|Telcred Personal]] app from anywhere)
	* Mobile on site (Open with the Telcred_Personal app when on site, as defined by the GPS coordinates for the site)		* Mobile on site (Open with the Telcred_Personal app when on site, as defined by the GPS coordinates for the site)
	* Mobile at door (Open with the Telcred_Personal app by scanning an NFC tag at the door)		* Mobile at door (Open with the Telcred_Personal app by scanning an NFC tag at the door)
	* API 1		* API 1
	* API 2		* API 2

			Mobile remote, Mobile on site, and Mobile at door all concern the [[Telcred_Personal\|Telcred Personal]] mobile app. Mobile remote allows the user to open from anywhere. Mobile on site allows the user to remote open doors when the user is on site. This is determined by comparing the phone's current GPS position with the coordinates for the site defined in [Site Manager]. Mobile at door allows the user to open a door by scanning an NFC tag at the door.

	The purpose of API 1 and API 2 are to let an external system request access by supplying the door identity and a credential identifier that could represent e.g. a license plate, a face, or the customer's own smartphone app.		The purpose of API 1 and API 2 are to let an external system request access by supplying the door identity and a credential identifier that could represent e.g. a license plate, a face, or the customer's own smartphone app.

Telcredstaff at 12:59, 17 January 2024

2024-01-17T12:59:16Z

← Older revision		Revision as of 12:59, 17 January 2024
Line 6:		Line 6:
	* PIN only		* PIN only
	* Mobile remote (Open with the [[Telcred_Personal\|Telcred Personal]] app from anywhere)		* Mobile remote (Open with the [[Telcred_Personal\|Telcred Personal]] app from anywhere)
	* Mobile on site (Open with the [[Telcred_Personal~~\|Telcred Personal]]~~ app when on site, as defined by the GPS coordinates for the site)		* Mobile on site (Open with the Telcred_Personal app when on site, as defined by the GPS coordinates for the site)
	* Mobile at door (Open with the [[Telcred_Personal~~\|Telcred Personal]]~~ app by scanning an NFC tag at the door)		* Mobile at door (Open with the Telcred_Personal app by scanning an NFC tag at the door)
	* API 1		* API 1
	* API 2		* API 2

Telcredstaff at 12:49, 17 January 2024

2024-01-17T12:49:26Z

← Older revision		Revision as of 12:49, 17 January 2024
Line 5:		Line 5:
	* Card + PIN		* Card + PIN
	* PIN only		* PIN only
	* ~~Remote~~ (~~The~~ [[Telcred_Personal\|Telcred Personal]] app)		* Mobile remote (Open with the [[Telcred_Personal\|Telcred Personal]] app from anywhere)
			* Mobile on site (Open with the [[Telcred_Personal\|Telcred Personal]] app when on site, as defined by the GPS coordinates for the site)
			* Mobile at door (Open with the [[Telcred_Personal\|Telcred Personal]] app by scanning an NFC tag at the door)
	* API 1		* API 1
	* API 2		* API 2

Telcredstaff at 12:28, 6 July 2022

2022-07-06T12:28:34Z

← Older revision		Revision as of 12:28, 6 July 2022
Line 26:		Line 26:

	Finally, select the door(s) the privilege should be able to open by selecting them in the list to the right and moving them over to the left by clicking the left arrow. It is possible to specify the doors that the privilege should open either by including the individual [[Doors\|doors]] or one or more [[Door groups\|door groups]]. It is perfectly fine to mix individual doors and door groups in the same privilege.		Finally, select the door(s) the privilege should be able to open by selecting them in the list to the right and moving them over to the left by clicking the left arrow. It is possible to specify the doors that the privilege should open either by including the individual [[Doors\|doors]] or one or more [[Door groups\|door groups]]. It is perfectly fine to mix individual doors and door groups in the same privilege.

	It is possible to share a privilege with another organization in the same system. Privilege sharing is explained in the section about [[Delegation\|delegation]].

Telcredstaff at 17:33, 4 November 2021

2021-11-04T17:33:59Z

← Older revision		Revision as of 17:33, 4 November 2021
Line 19:		Line 19:
	Start by giving the privilege a meaningful name.		Start by giving the privilege a meaningful name.

	The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]]. ~~If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type ''Regular'', it~~ is ~~the~~ ~~controller~~ ~~that~~ ~~makes the access control decision~~.		The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]] and is further explained [[SmartIntego settings\|here]].

	Select which credential should be used. For privileges of type ''Use whitelist where possible'' the only credential type available is ''card only''.		Select which credential should be used. For privileges of type ''Use whitelist where possible'' the only credential type available is ''card only''.

Telcredstaff at 16:10, 13 October 2021

2021-10-13T16:10:37Z

← Older revision		Revision as of 16:10, 13 October 2021
Line 17:		Line 17:


	Start by giving the privilege a meaningful name~~. A good name indicates which door(s) the privilege opens and with which credential (e.g. card + PIN)~~.		Start by giving the privilege a meaningful name.

	The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]]. If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type ''Regular'', it is the controller that makes the access control decision.		The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]]. If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type ''Regular'', it is the controller that makes the access control decision.

Telcredstaff at 16:09, 13 October 2021

2021-10-13T16:09:38Z

← Older revision		Revision as of 16:09, 13 October 2021
Line 14:		Line 14:


	[[File:create-privilege.png\|Create privilege]]		[[File:create-privilege.png\|border\|Create privilege]]

Telcredstaff at 16:15, 27 October 2020

2020-10-27T16:15:43Z

← Older revision		Revision as of 16:15, 27 October 2020
Line 21:		Line 21:
	The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]]. If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type ''Regular'', it is the controller that makes the access control decision.		The next parameter is ''type'', and there are two options: "Regular" and "Use whitelist when possible". The whitelist option is only relevant for doors with locks from [[SimonsVoss SmartIntego]]. If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type ''Regular'', it is the controller that makes the access control decision.

	Select which credential should be used ~~and optionally a schedule during which the privilege should be active~~. For privileges of type ''Use whitelist where possible'' the only credential type available is ''card only'' ~~and it is not possible to specify a schedule~~.		Select which credential should be used. For privileges of type ''Use whitelist where possible'' the only credential type available is ''card only''.

			''Active'' can be either ''Always'' or ''Only during...'' (specified by a schedule). For privileges of type ''Use whitelist where possible'' it is not possible to specify a schedule.

	Finally, select the door(s) the privilege should be able to open by selecting them in the list to the right and moving them over to the left by clicking the left arrow. It is possible to specify the doors that the privilege should open either by including the individual [[Doors\|doors]] or one or more [[Door groups\|door groups]]. It is perfectly fine to mix individual doors and door groups in the same privilege.		Finally, select the door(s) the privilege should be able to open by selecting them in the list to the right and moving them over to the left by clicking the left arrow. It is possible to specify the doors that the privilege should open either by including the individual [[Doors\|doors]] or one or more [[Door groups\|door groups]]. It is perfectly fine to mix individual doors and door groups in the same privilege.