Delegation: Difference between revisions

From Telcred documentation
Jump to navigation Jump to search
(Redirected page to Site Manager)
Tag: New redirect
 
(30 intermediate revisions by the same user not shown)
Line 1: Line 1:
#REDIRECT [[Site Manager]]
== Officers and capacities ==

The people involved with the administration of a system are referred to as ''officers''. An officer can have one or more of the following ''capacities'':

* System owner
** Create and edit organizations
** Create and edit new officers
** Assign officers to be system owners, organization owners, and administrators

* Organization owner (for one or more organizations)
** Edit organization
** Create and edit new officers
** Assign officers to be organization owners, and administrators

* Administrator (for one or more organizations)
** Monitor events
** Manage access rights, i.e. doors, users, devices, schedules...
** Configure door groups and hardware

== Administrator views ==

The administrator GUI is separated into three different ''views'' that mirror the capacities system owner, organization owner, and administrator. For a large installation, these may be used by different people. For a smaller installation, it is likely that the same person(s) will use all three views, but for different things.

=== System owner ===

This view is accessible to officers with the ''system owner'' capacity, and is available at:

https://access.telcred.com/sys


[[File:sysowner.png|System owner]]


When creating a new organization, the system owner specifies the default time zone (can be changed for individual door controllers). In the same screen, the system owner can assign officers to be organization owners and / or administrators.

The system owner can also appoint other officers to be system owners. This is done when creating or editing an officer. In the same screen it is also possible to assign the officer to be organization owner for one or more organizations:


[[File:sysownerofficer.png|Create system owner]]


Telcred Access Manager supports two-factor authentication for officer login and we highly recommend to use it. The only method currently supported is [https://www.yubico.com/products/services-software/personalization-tools/yubikey-otp/ Yubikey OTP] (One Time Password). More information about two-factor authentication can be found [[Two-factor authentication|here]].

An officer can be temporarily blocked, in which case he or she will not be allowed to login.

=== Organization owner ===

This view is accessible to officers with the ''organization owner'' capacity, and is available at:

https://access.telcred.com/org


[[File:orgowner.png|Organization owner]]


An organization owner can edit the organization name and default time zone, and assign officers to be organization owners and / or administrators (for the current organization). Assigning officers can be done when updating the organization information OR when creating or editing officers:

[[File:createorgofficer.png|Create organization officer]]

=== Administrator ===

This is the normal administrator view, where an officer with the ''administrator'' capacity can add new users, assign access rights to users, etc. This view is available at:

https://access.telcred.com

== Switching between organizations ==

One officer can be administrator or organization owner in several organizations. In this case, the officer can switch between organizations using the selector at the top of the screen:

[[File:switch_org.png|Switch organization]]

== Sharing between organizations ==

=== Doors ===

With delegation, each organization can manage their own users, doors, and access rights. However, it is common that users belonging to one organization need access rights to doors belonging to another organization. For example, in an office building with tenants, all tenants need access to the entrance doors to the building, as well as garages, and elevators.

One way to address this need is through ''door sharing''. The administrator of organization A can share a door with organization B, which makes it possible for the administrator of organization B to create privileges for that door as if it were their own (but not change any settings for the door).


[[File:doorsharing.png|Door sharing]]

=== Privileges ===

Sometimes there is a need for more fine-grained control of when and how a shared door can be accessed by the users of other organizations. For example, the building owner may want to share the door to a common storage room with all the tenants, but only during office hours. For these cases, Telcred Access Manager has privilege sharing. The administrator of a door can create a privilege (with its credential and optional schedule restriction) and then share it with other organizations. The administrator(s) of the organization(s) can then assign this privilege to their own users via a role just as for their own privileges.


[[File:policysharing.png|Privilege sharing]]

=== User sharing ===

User sharing solves another use case, namely when a user belonging to one organization often needs access to doors belonging to another organization. For example, the building owner can create a user for service staff and then share this user with all the tenants. This allows the tenants to maintain control of when service staff can access their premises.


[[File:User sharing.png|User sharing]]

Latest revision as of 11:55, 9 April 2023

Redirect to: