This page provides an overview of identity groups, the types of groups, and how their members are determined.
Overview
Identity groups let you group the identities managed in Josys, either by conditions or by selecting them individually. Once created, an identity group can be used as a shared definition whenever a Josys feature asks you to specify which identities it applies to.
Currently, you can apply identity groups in the Policies feature. Reference: What Are Policies?
With identity groups, you can:
- Standardize target definitions: Instead of specifying target identities with conditions each time in each feature, you can select an existing identity group.
- Handle employee, external, and system accounts separately: Based on "Identity Type", identities are automatically sorted into three groups: "Employees", "External", and "System".
- Keep membership up to date automatically: For identity groups created with conditions, members are automatically updated when an identity's department, identity type, or other attributes change.
Intended Audience
IT administrators
Types of Identity Groups
There are two types of identity groups: "system groups" and "custom groups".
System Groups
System groups are identity groups provided by Josys. In the identity group list, the three groups "Employees", "External", and "System" are shown together under the "System Categories" row.
Each identity is assigned to exactly one system group based on its "Identity Type" value. The default mapping is as follows.
| System group | Identity types assigned (default) |
|---|---|
| Employees | Full-time, Board Member, Transferee |
| External | Contractor, Subcontractor, Temporary Employee |
| System | System, Others |
- An identity never belongs to more than one system group.
- You can change which identity types are assigned to which system group to fit your company's operations. You can also restore the default mapping.
- System groups cannot be deleted or renamed.
Reference: Create, Edit, and Delete Identity Groups ("4. Edit the System Group Mapping")
Custom Groups
Custom groups are identity groups that you create. An identity can belong to multiple custom groups.
When you create a custom group, you choose how its members are determined from three options: "Condition Based", "Fixed", and "All Identities".
Types of Membership Logic
The "Membership Logic" column in the identity group list shows how the members of each group are determined.
| Shown in the "Membership Logic" column | Option selected at creation | Description |
|---|---|---|
| Condition Based | Condition Based | Consists of identities that match the specified conditions. When the identities matching the conditions change, the members are updated automatically. |
| Fixed | Fixed | Consists of individually selected identities. |
| All Identities | All Identities | Consists of all identities in Josys. |
| Mapping Based | None (system groups) | Consists of identities assigned through the identity type mapping. |
How "Condition Based" Conditions Are Evaluated
With "Condition Based", you can use the following fields as conditions:
- Employment Status
- Identity Type
- Department
- Location
- Job Title
For each condition, select the operator "is" or "is not" and specify values. Multiple conditions and values are evaluated according to the following rules:
- If you add multiple conditions, identities that meet all of the conditions become members (AND).
- If you specify multiple values for one condition, the condition is met if any of the values matches (OR).
- Each identity group can have only one condition per field.
Example: If you set two conditions, "Department is Sales, Marketing" and "Identity Type is Full-time", full-time employees in the Sales or Marketing department become members.
Automatic Membership Updates
Identity group members are updated automatically at the following times:
| When | Scope of the update |
|---|---|
| When an identity group is created or edited, or the system group mapping is changed | The entire identity group |
| When an identity is registered or edited in Josys, or a department is deleted | The groups the affected identities belong to |
| Changes from synchronization with external systems, such as External Data Sources | Applied together by an update process that runs once a day |
Labels Used on Screens
In the English UI, this feature is called "Identity Groups" throughout, although the exact label differs slightly depending on the screen. All of these refer to the same feature.
| Screen | Label |
|---|---|
| Left sidebar, identity group list, and the target identity conditions in policies | Identity Groups |
| Column name in the identity list, and the menu in the upper right of the identity list | "Identity Group" (column name) and an identity group management option (menu) |
| Screen for selecting an existing group in a policy | An option to select an identity group |
Identity Group Use Cases
| Use case | Identity group to use |
|---|---|
| Apply an account deletion policy for offboarding only to the accounts of contractors, subcontractors, and temporary employees | The "External" system group |
| Group identities that are in the "Sales" department and are "Full-time", so that membership automatically follows transfers and employment type changes | A group created with "Condition Based" |
| Group identities that cannot be described by attributes, such as identities involved in audits or project members | A group created with "Fixed" |
| Match your company's own classification rules, such as treating contractors as employees | Edit the system group mapping |
Limitations and Notes
- Five fields can be used with "Condition Based": Employment Status, Identity Type, Department, Location, and Job Title. Custom fields and dates cannot be used as conditions.
- Conditions on different fields cannot be combined with "OR".
- Identity groups that are in use by a policy cannot be deleted.
- Groups from external services such as Microsoft Entra ID and Google Workspace cannot be imported as identity groups.
FAQ
Q: What is the difference between departments and identity groups?
A department is one of an identity's attributes. An identity group groups identities based on conditions across multiple fields, including department, or by individual selection, so that Josys features can target them.Q: Can an identity belong to multiple identity groups?
An identity can belong to multiple custom groups, but to only one system group.Q: Can I use groups from Microsoft Entra ID or Google Workspace as they are?
Not at this time. Please create identity groups in Josys.Q: Which features can use identity groups?
Currently, you can use them in "Policies" to specify which identities a policy applies to. If support is added to other features, we will announce it on this page.