Assa Abloy TRAKA32, Руководство пользователя

Страница: 303 / 919

V3.5 14/08/19 UD0089 Page 303
This Document is uncontrolled unless over stamped "CONTROLLED DOCUMENT"
3.9.2.4 REGIONS
3.9.2.4.1 REGION OVERVIEW
Regions allows for Traka32 Administrators to see and access only the information from Systems, iFobs, Keys and Users
within their specified region(s). In addition it allows Traka system cabinet users to only access the cabinets within their
specified region(s).
From Traka32 Version 02.07.0001, Region functionality has been significantly improved to allow users to belong to
Multiple Regions. Prior to Traka32 Version 02.07.0001, a user could only belong to a single region. Click
here for a
graphic of single regions operation.
Multiple Regions provides much increased flexibility for customers with more complex software and system access
requirements. An example of where Multiple Regions maybe necessary, is where an organisation has many Traka
systems spread geographically and each region has one or more Traka32 Administrators that are only responsible for
maintaining their own Region(s). The Traka systems could be spread over a county, country, a continent or even all
over the world using a Wide Area Network (WAN). In addition some organisations may choose to regionalise by
department i.e. Sales, Finance, Engineering, where each department has a Traka32 Administrator who can only see
Traka Systems and Users within their department(s).
Following is a graphic representing how a Multiple Region system may be defined.
It is important to note the following...

A Traka system can only belong to a single Region. It has a fixed location.

A Traka user may belong to Multiple Regions. Users are not fixed and may move around from region to
region.
Coupled with the Multiple Security Groups (that can belong to Regions) facility, it makes for ultimate flexibility over
your Traka system administration.