Users
The Team › Users section lists the people who can sign in to FiveGuardian5, either to connect their device or to administer the panel. For each user you will see their name, email, role, status and assigned groups.
A user's groups are inherited by the devices they register, so assigning user groups correctly is the simplest way to control their access. See Policies and groups.
Adding users
There are two common ways for a person to get an account:
- Sign-in with the identity provider: the person signs in with their company account (for example, Google) and their user is created in FiveGuardian5. Depending on configuration, it may require approval.
- Created from the panel: an administrator creates or invites the user from Team › Users.
With the identity provider sync module, users and groups can be kept in sync automatically. See Integrations.
User approval
New users may need administrator approval before getting access. This prevents anyone with an account in the domain from joining the network automatically. When a user is pending, check that they are an active employee and approve them from Team › Users. Reject or delete requests you do not recognize.
Authentication settings
Settings › Authentication defines parameters such as approval of new users or devices and session expiration, which forces users to re-authenticate periodically. Shorter expiration increases security but shows the sign-in window more often. Coordinate with the FiveGuardian5 support team before changing these values, because they affect every user.
Roles and permissions
Each user has a role that determines what they can see and do in the panel. Regular users only connect their device; administrators manage the configuration. Under Settings › Permissions you can review the scope of each role.
- Apply least privilege: grant the administrator role only to those who need it.
- Review the list of administrators periodically.
- Block or delete users who leave the organization immediately.
Service users
Team › Service Users holds technical accounts not tied to a person, intended for automations that use the API. Give each one the minimum role needed, document why it exists and delete the ones no longer in use.