Main Page - Revision history

Telcredstaff: /* Example */

2024-11-11T14:43:04Z

Example

← Older revision		Revision as of 14:43, 11 November 2024
Line 131:		Line 131:
	==== Example ====		==== Example ====

	A real estate company sets up two Systems for buildings in two different locations and lets the respective Site Manager define Domains representing the spaces being let out to tenants. Upon moving in, each tenant receives their own virtual system (Sub-system) connected to the Domain(s) representing the spaces they are renting. One tenant is renting spaces (Office 2 and Office 5) in two different Sites but by connecting these two Domains to ~~System~~ 3, they can manage the two offices ~~as one~~.		A real estate company sets up two Systems for buildings in two different locations and lets the respective Site Manager define Domains representing the spaces being let out to tenants. Upon moving in, each tenant receives their own virtual system (Sub-system) connected to the Domain(s) representing the spaces they are renting. One tenant is renting spaces (Office 2 and Office 5) in two different Sites but by connecting these two Domains to a Virtual system, they can manage the two offices together.

	Systems and Domains are created, organized and maintained in [[Main Page#Introduction to System Manager\|System Manager]].		Systems and Domains are created, organized and maintained in [[Main Page#Introduction to System Manager\|System Manager]].

Telcredstaff: /* Account, Systems, and delegation */

2024-11-11T14:41:17Z

Account, Systems, and delegation

← Older revision		Revision as of 14:41, 11 November 2024
Line 109:		Line 109:
	=== Account, Systems, and delegation ===		=== Account, Systems, and delegation ===

	A Telcred customer account can contain one or more Systems. A system contains doors, users, access rights, schedules, events etc, and has its own administrators. The purpose of this structure is “delegation of access administration”, i.e. to let administrators with direct knowledge of, and responsibility for, their users perform the administration without relying on a centralised administration function. A typical example of where delegation can be useful is an office building with multiple tenants. The delegation functionality allows each tenant to manage their own users and access rights without ~~relying~~ on the building's owner.		A Telcred customer account can contain one or more Systems. A system contains doors, users, access rights, schedules, events etc, and has its own administrators. The purpose of this structure is “delegation of access administration”, i.e. to let administrators with direct knowledge of, and responsibility for, their users perform the administration without relying on a centralised administration function. A typical example of where delegation can be useful is an office building with multiple tenants. The delegation functionality allows each tenant to manage their own users and access rights without being dependent on the building's owner.

	==== System types ====		==== System types ====

Telcredstaff: /* Account structure and delegation */

2024-11-11T14:40:39Z

Account structure and delegation

← Older revision		Revision as of 14:40, 11 November 2024
Line 107:		Line 107:
	== Account structure and delegation ==		== Account structure and delegation ==

	=== Account, Systems, ~~Domains,~~ ~~Sub-systems~~ ===		=== Account, Systems, and delegation ===

	A Telcred customer account can contain one or more Systems. A system contains doors, users, access rights, schedules, events etc. A ~~system~~ ~~can~~ ~~also~~ ~~contain~~ ~~sub-systems,~~ ~~which~~ ~~contain~~ ~~their~~ ~~own~~ ~~users,~~ access ~~rights~~, ~~schedules,~~ ~~events~~, and so on, ~~but~~ the ~~doors~~ ~~come~~ ~~from~~ the ~~parent~~ ~~system~~.		A Telcred customer account can contain one or more Systems. A system contains doors, users, access rights, schedules, events etc, and has its own administrators. The purpose of this structure is “delegation of access administration”, i.e. to let administrators with direct knowledge of, and responsibility for, their users perform the administration without relying on a centralised administration function. A typical example of where delegation can be useful is an office building with multiple tenants. The delegation functionality allows each tenant to manage their own users and access rights without relying on the building's owner.

		⚫	==== System types ====
	The purpose of this structure is “delegation of access administration”, i.e. to let administrators with direct knowledge of, and responsibility for, their users perform the administration without relying on a centralised administration function. A typical example of where delegation can be useful is an office building with multiple tenants. The delegation functionality allows each tenant to manage their own users and access rights without relying on the building's owner.

			There are four types of systems:
⚫	==== ~~Systems~~ ====
			* Standard
			* Standard with delegation
			* Virtual
			* Sub-system

			A standard system contains all functionality, including hardware configuration, except delegation. A standard system with delegation also provides the opportunity to create Sub-systems and share doors with Virtual systems (see below).
	A System typically represents a building or a group of buildings with a shared facility management. Under the System, Domains and Sub-systems are created and maintained if delegated access management is used. An Account always includes at least one system which is used for configuring the doors that can be allocated to the Domains of the Site.

			A virtual system does not have any own hardware, but instead gets doors from other systems of type Standard with delegation. A typical use case for a virtual system is an organization where the employees visit many different sites.
	A System without Domains works as a regular access control system. It can still be connected connect to Domains of other Systems and that way, doors from different Systems can be administered together.

			Sub-systems also must get their doors from somewhere else, but in this case they can only get doors from the parent system of which they are a part. A typical use case for a Sub-system is a tenant.

	==== Domains ====		==== Domains ====

	Domains represent spaces such as offices, business premises, apartments, workshops, garages etc. A Domain can contain private doors, shared doors, and shared privileges. By connecting a Domain to a Sub-system or a ~~System~~, the doors and privileges of the Domain become available for access administration in the receiving system.		Domains represent spaces such as offices, business premises, apartments, workshops, garages etc. A Domain can contain private doors, shared doors, and shared privileges. By connecting a Domain to a Sub-system or a Virtual system, the doors and privileges of the Domain become available for access administration in the receiving system.

	==== Sub-systems ====

	Tenants or other user groups, receive their own System or Sub-system, which they can administer on their own.

	==== Example ====		==== Example ====
Line 131:		Line 133:
	A real estate company sets up two Systems for buildings in two different locations and lets the respective Site Manager define Domains representing the spaces being let out to tenants. Upon moving in, each tenant receives their own virtual system (Sub-system) connected to the Domain(s) representing the spaces they are renting. One tenant is renting spaces (Office 2 and Office 5) in two different Sites but by connecting these two Domains to System 3, they can manage the two offices as one.		A real estate company sets up two Systems for buildings in two different locations and lets the respective Site Manager define Domains representing the spaces being let out to tenants. Upon moving in, each tenant receives their own virtual system (Sub-system) connected to the Domain(s) representing the spaces they are renting. One tenant is renting spaces (Office 2 and Office 5) in two different Sites but by connecting these two Domains to System 3, they can manage the two offices as one.

	Systems~~, Domains,~~ and ~~Sub-systems~~ are created, organized and maintained in [[Main Page#Introduction to System Manager\|System Manager]].		Systems and Domains are created, organized and maintained in [[Main Page#Introduction to System Manager\|System Manager]].

	=== Administrators and capacities ===		=== Administrators and capacities ===

Telcredstaff: /* Privileges */

2024-10-11T11:07:07Z

Privileges

← Older revision		Revision as of 11:07, 11 October 2024
Line 322:		Line 322:
	Privileges express access rights, i.e. the right to open one or more doors. A privilege is defined by a combination of:		Privileges express access rights, i.e. the right to open one or more doors. A privilege is defined by a combination of:
	* one or more doors		* one or more doors
			* one or more credentials
	* a schedule		* an optional schedule
	* a credential


	The supported credential types are:		The supported credential types are:

Telcredstaff: /* Account, Systems, Domains, Sub-accounts */

2024-10-11T11:05:54Z

Account, Systems, Domains, Sub-accounts

← Older revision		Revision as of 11:05, 11 October 2024
Line 107:		Line 107:
	== Account structure and delegation ==		== Account structure and delegation ==

	=== Account, Systems, Domains, Sub-~~accounts~~ ===		=== Account, Systems, Domains, Sub-systems ===

	A Telcred customer account can contain one or more Systems. A system contains doors, users, access rights, schedules, events etc. A system can also contain sub-systems, which contain their own users, access rights, schedules, events, and so on, but the doors come from the parent system.		A Telcred customer account can contain one or more Systems. A system contains doors, users, access rights, schedules, events etc. A system can also contain sub-systems, which contain their own users, access rights, schedules, events, and so on, but the doors come from the parent system.

Telcredstaff: /* Systems */

2024-09-19T19:34:36Z

Systems

← Older revision		Revision as of 19:34, 19 September 2024
Line 189:		Line 189:
	A system can also have one or more Domains which typically represent a physical space that is leased to a a tenant. For each domain, Private Doors, Shared Doors, and Cards can be defined. The current receiver of a domain (a System or Sub-system) will have access to these resources.		A system can also have one or more Domains which typically represent a physical space that is leased to a a tenant. For each domain, Private Doors, Shared Doors, and Cards can be defined. The current receiver of a domain (a System or Sub-system) will have access to these resources.

	For every system, there is a Card Management feature available. This enables an administrator to create and assign cards Domains and Sub-systems.		For every system, there is a Card Management feature available. This enables an administrator to create and assign cards to Domains and Sub-systems.

	=== Sub-systems ===		=== Sub-systems ===

Telcredstaff: /* Login context */

2024-09-19T19:32:17Z

← Older revision		Revision as of 19:32, 19 September 2024
Line 214:		Line 214:


	If you have access to more than one Account, it is possible to switch between them using the dropdown-menu to the right of the Account name. Likewise, if the Account has more than one System, and the ~~administrator~~ has administration rights in more than one of the Systems, it is possible to switch System using the dropdown-menu to the right of the System name.		If you have access to more than one Account, it is possible to switch between them using the dropdown-menu to the right of the Account name. Likewise, if the Account has more than one System, and the Administrator has administration rights in more than one of the Systems, it is possible to switch System using the dropdown-menu to the right of the System name.

	To access the ~~officer~~ settings, e.g. to change password, expand the menu right next to the currently logged in ~~administrator~~.		To access the Administrator settings, e.g. to change password, expand the menu right next to the currently logged in Administrator.

	=== Four main menu groups ===		=== Four main menu groups ===

Telcredstaff: /* List pages and detail pages */

2024-09-19T19:30:52Z

List pages and detail pages

← Older revision		Revision as of 19:30, 19 September 2024
Line 236:		Line 236:


		⚫	In the left hand column of the detail page, the item is displayed with its current attributes. In the right hand column there is more information about the current item, such as its current status, available actions, and related items.
	[[File:Door_list2.png\|800px\|List page]]


⚫	In the left hand column of the detail page, the item is displayed with its current attributes. In the right hand column there is more information about the current item, such as its current status, available actions, and related items.


	[[File:Door_details2.png\|800px\|Detail page]]

	== Administrator GUI menu options ==		== Administrator GUI menu options ==

Telcredstaff: /* Login context */

2024-09-19T19:29:48Z

← Older revision		Revision as of 19:29, 19 September 2024
Line 214:		Line 214:


	If you have access to more than one Account, it is possible to switch between them using the dropdown-menu to the right of the Account name. Likewise, if the Account has more than one System ~~(see the section on [[Delegation\|delegation]])~~, and the administrator has administration rights in more than one of the Systems, it is possible to switch System using the dropdown-menu to the right of the System name.		If you have access to more than one Account, it is possible to switch between them using the dropdown-menu to the right of the Account name. Likewise, if the Account has more than one System, and the administrator has administration rights in more than one of the Systems, it is possible to switch System using the dropdown-menu to the right of the System name.

	To access the officer settings, e.g. to change password, expand the menu right next to the currently logged in administrator.		To access the officer settings, e.g. to change password, expand the menu right next to the currently logged in administrator.

Telcredstaff: /* Login context */

2024-09-19T19:26:08Z

← Older revision		Revision as of 19:26, 19 September 2024
Line 217:		Line 217:

	To access the officer settings, e.g. to change password, expand the menu right next to the currently logged in administrator.		To access the officer settings, e.g. to change password, expand the menu right next to the currently logged in administrator.

	More information about the administrator settings can be found [[Administrator settings\|here]].

	=== Four main menu groups ===		=== Four main menu groups ===