Functional management of users, roles, permissions, groups, and invitations to operate shared environments in a controlled way.
Functional purpose
Users and Community organizes how people access, manage, and share Horus environments. This domain allows owners, administrators, and guests to collaborate on the same instance without losing control over permissions, visibility, and responsibilities.
Operating value
User management makes it possible to share Horus capabilities with internal teams, neighbors, customers, providers, or response teams without granting full access to the environment. Groups reduce administrative load and make it possible to apply permissions, notifications, and schedules to sets of people.
Included capabilities
| Capability | Explanation |
|---|---|
| Self-registration | Allows new users to create their account and join the Horus ecosystem in a controlled way. |
| Multi-user environments | Enables the same instance to be operated by several people according to their responsibilities and permissions. |
| Role-based access control | Defines what each user can do based on functional profiles tied to their responsibility level. |
| Owner / Administrator / Guest profiles | Organizes operations between environment owners, administrators with delegated control, and guests with limited access. |
| Granular permissions | Enables specific access by device, function, view, group, or scenario according to operating needs. |
| Shared environment management | Makes it easier to share a Horus instance with other users without losing control over ownership, permissions, and visibility. |
| User invitation system | Allows authorized users to add people to an environment through managed invitations. |
| Community-based collaboration | Turns devices and views into resources that can be shared with users, neighbors, institutions, or operations teams. |
| Group creation and management | Groups users to simplify the assignment of permissions, notifications, and operating rules. |
| Permission delegation through groups | Applies permissions to full teams, avoiding individual access management when operations are shared. |
| Shared operational agendas | Coordinates calendars, access windows, and operating hours between authorized users or groups. |
| Multi-instance ownership | Allows the same user to own or administer more than one Horus environment. |
Relationship with the Horus ecosystem
This domain connects with security, dashboards, schedules, and automations. Permissions defined for users or groups determine which devices are visible, which actions can be executed, which notifications are received, and which operating scenarios are available.