Managing Group Members

New members can be added to the group at any time. The maximum number of group members is not limited. When a group is deleted, its members are not destroyed.

An object may belong to several groups.

Note for advanced Iotellect administrators: group members cannot be accessed by context paths such as group_context_path.member_name. Instead, the normal paths of group members should be used to access them. For example, even if we put the admin user in the usergroup1 group, we won't be able to access it using a path such as usergroups.usergroup1.admin. It may be accessed by its normal path: users.admin.

Group members may be added to a group in Iotellect Server User Interfaces by dragging a context and dropping it on a group. If the context type is suitable for the group, it will be added. More information about the logic behind this operation may be found here.

Every group member context has a Remove from group action (), which may be accessed through its context menu in the Iotellect Client System Tree or through similar facilities in other clients.

Groups support unlimited nesting, i.e., one group may be a member of another group, which is, in its turn, a member of a third one, etc.

Membership information is exposed in two different ways:

• Static Members (staticMembers) contain only direct members explicitly added to the group (users, devices, or subgroups).

• Group Membership (groupMembership) describes the effective membership of the current context in nested groups. For a context that belongs to a nested subgroup, groupMembership includes the subgroup and the full chain of its parent groups up to the top-level (root) group.

Was this page helpful?

Tell us more

Send

Thank you!