Best practices when designing a customer system

When designing a customer system, a well-planned premises structure along with a methodical role management process are essential – also for future changes.

The role of the main user

The main user is an individual responsible for the customer system. Each customer system must have at least one main user, but it can also have several main users. A real person must always be appointed as the main user. This person maintains the customer system throughout its lifecycle. The main user can be changed at any time.

The main user has the highest level of rights in the customer system. They have the right to perform administrative actions on all premises in the customer system.

Considerations for creating a premises structure

Refer to the list below for important factors to take into consideration when planning a premises structure for your customer system:

1. Understand premises as administrative and logical entities
   • Division of buildings/sites: Visualize how buildings or sites can be divided into manageable entities.
   • Roles and access: Determine roles for people accessing and administrating the premises.
2. Plan from large entities to smaller ones
   • Size and number: Consider the size and number of buildings or sites.
   • Geographical division: Premises can be divided into administrable entities based on geographical location, for example.
   • Dividing buildings: In the multifamily residential segment, buildings can be divided into apartments, communal spaces, corridors, etc.
   • Administration: Assign different administrators to specific buildings or sites for focused management.
3. Movement and traffic flow
   • Flow of traffic: Consider how people will move around the premises. Pay attention to the flow of traffic through common areas such as lobbies and corridors.
   • Connectivity: Think about how different areas are connected and lead to one another.
4. Access points
   • Secured areas: Typically, premises are secured with access points.
   • Non-secured areas: You do not necessarily need to create premises for areas without access points.

Considerations for creating roles

In the iLOQ 5 Series+ Manager, there are two types of roles: administrator roles and user roles. Administrator roles only have system-level rights i.e., can perform administrative actions with iLOQ 5 Series+ Manager, they do not have physical access to any premises.

User roles only have physical access to premises, they cannot log in to or perform any administrative actions with iLOQ 5 Series+ Manager.

Refer to the list below for important factors to take into consideration when planning roles for your customer system:

1. Apply the principle of least privilege
   • The principle of least privilege is a fundamental component of role-based access control. This guideline specifies that individuals should be granted the minimum level of rights necessary to fulfill their responsibilities.
2. Define administrator roles
   • Clearly define who will manage what, such as building managers or key administrators.
   • Rights limitation: Ensure each administrator role has rights only to administer the necessary premises and can perform only the actions they need to.
3. Define user roles
   • Identify which user roles need access to specific premises, such as cleaning or maintenance staff.
   • Physical access limitation: Assign each user role access only to the necessary premises for their tasks.

• PreviousDeployment guide
• NextHow to deploy a customer system