Team Management in Connect

Summary

Selora Connect is the primary workspace for professional installers. Today, an installer account is effectively a single identity: everyone on the team works under one login, and nobody in the team can manage who has access. Team management introduces first-class user accounts and roles inside an installer account, so installers can invite their employees, attribute different roles to each of them, and control what each person can do based on those roles.

Value

• Shared account, not shared identity: Employees join the installer account with their own login instead of sharing one.
• Least privilege by default: Each employee only gets the permissions their work requires.
• Reduced risk: Account-wide and sensitive operations stay reserved for account admins.
• Auditability: Actions are attributed to a named user instead of a shared login.

Scope

Phase 1 keeps the role model deliberately simple:

• Account admins can invite and remove employees, assign roles, and manage account-level settings.
• Employees get a personal account within the installer account and work within the permissions of the role they are assigned.
• Profile edits are reserved to account admins. No one else can edit a profile — including their own — in phase 1.

Initial roles and permissions:

The permission model is designed so additional fine-grained permissions (property access, billing, data export, …) can be granted to roles in later phases without changing how roles work.

Target customers

• Professional installers with employees or subcontractors
• Integrators who manage a team of field technicians

Open questions

• Which role should be assigned by default when a new employee is invited?
• Which permissions beyond profile edits should be gated in phase 1 (property access, billing)?
• Is an audit log of role and membership changes needed in phase 1?

Related

• RBAC Selora AI and MCP (Epic #57): GitLab epic #57
• Multi-property management (Epic #26): GitLab epic #26