What elements are required for basic setup and functioning?

The main elements are groups, users, identifiers, access restrictions, and connections between them. These are the basic elements that must be configured at the beginning.

Core system elements

• Groups
  Define the hierarchical structure and access boundaries. Each project must start with a manually created root group. All other elements — devices, users, identifiers — are linked to groups.

  The group hierarchy defines data visibility and access control:

  • Users in child groups cannot view or configure entities from parent groups.

  • Group administrators can only manage resources within their own group and its descendants.

  ➤ No user or device can be added without being assigned to a group.

• Users
  Represent real people in the system — residents, administrators, or concierges. Users are assigned to groups and granted access via identifiers and permissions.

• Profiles
  Define what a user can see and do in the system. A profile is a set of permissions that grants access to specific actions — for example, adding users, managing devices, or configuring access rules. Profiles are usually predefined and aligned with system-level permissions.

• Licenses
  Define which features are available in the system. Licenses grant access to SIP calls, mobile app usage, remote door opening, integrations, and more.
  Licenses are uploaded manually and managed centrally via Settings → Licenses tab. Limits can be applied at both user and group levels.

Service logic and feature activation

• Identifiers
  Allow physical or digital access. Supported types include RFID or NFC cards, mobile apps via UKEY, license plates, access codes, QR codes for guests, biometric methods like Face ID, and credentials from third-party systems.
  Each identifier is linked to a user and must be added only after access restrictions are in place.

• Access restrictions
  Define where, when, and how users can interact with devices — for example, which door, time of day, or elevator floor.

• Devices
  Include entrance panels, indoor monitors, indoor audio phones, guard units, and access control devices. Devices are linked to groups and must be properly configured to receive updates and enforce access rules.

• Forwarding rules
  Control how intercom calls or access attempts are routed — to mobile apps, concierge panels, external numbers, or specific devices.
  Rules follow group logic and allow flexible call distribution based on the system structure.

• Virtual numbers
  Used for intercom calls and call routing. Virtual numbers can be assigned to apartments, users, entrance panels, or monitors, and are linked to forwarding rules.

• Elevators
  Managed as part of access control. Access to floors is defined via identifiers and permissions.

• Guest access
  Allows issuing temporary identifiers with limited access, such as time-bound QR codes.

• Schedules
  Time-based access rules that allow or restrict entry during certain hours or days.

• Access matrix
  Advanced tool to manage and visualize access rights across multiple users and devices.

🔹 Getting started

To launch a project on BAS-IP Link, follow these steps:

1. Create a root group to begin building the project structure.
   The root group is not created automatically and must be added manually before any other configuration.

2. Build a group hierarchy using logical levels such as Building, Unit, Floor, and Apartment to reflect the layout of the site. Use the Custom type for partner projects or non-residential objects.

3. Assign licenses in Settings → Licenses to activate required system features.

4. Add devices and link them to appropriate groups.

5. Add users and place them into the corresponding groups.

6. Set access restrictions to control who can access what and when.

7. Assign identifiers such as cards, UKEY, access codes, or QR codes.

👉 Continue with the FAQ list for specific setup instructions.