Users and usergroups

Sky View can operate with or without user management. When user management is disabled, anyone who accesses the system has administrator privileges and can view and control all platforms and settings. When user management is enabled, each person must log in with their own account and can be assigned one of two roles:

  • Administrator – full access to all configuration and data
  • User – restricted access according to assigned usergroups and platform permissions

Sky View lets administrators control who can log in and what they can see by combining users and usergroups. This guide explains the relationship between those concepts, the built-in administrator account, and how platform access is granted.

Enabling or disabling user management

User management can be enabled or disabled in the Server configuration section under the Server tab.

👤 Users

A user represents an individual person who can sign in to the Sky View web interface. Each user record stores the person's credentials and contact details and can be assigned to one or more usergroups to inherit permissions.

More on users configuration

👥 Usergroups

A usergroup is a reusable collection of permissions. Instead of configuring the same privileges repeatedly for every person, you assign users to the appropriate usergroups. When permissions change, update the usergroup once and every member automatically receives the new capabilities.

More on usergroups configuration

Platform access

Usergroups are also used to control access to the platforms that Sky View aggregates. Every usergroup can be granted access to one or more platforms. By default, new usergroups are granted All platforms. Adjust this list to limit a group's visibility to only the relevant platforms.

🔐 Administrator account

Sky View ships with a built-in administrator account to help you perform the initial setup:

  • Username: admin
  • Password: admin

The administrator has full access to every platform and configuration area. Immediately change the default password after the first login. Leaving the default credentials in place exposes your deployment to unauthorized access.

To change the password, sign in as the administrator, open the user management page, edit the admin user, and set a strong, unique password. Consider creating an additional personal administrator account and disabling or restricting the shared default account once setup is complete.