Manage users and roles via Active Directory
Provision Simetrik roles for your organization's users through Microsoft Entra ID (Azure AD) security groups.
Manage users and roles via Active Directory
If your organization uses Microsoft Entra ID (Azure Active Directory), you can manage who has access to Simetrik — and what role they have — directly from your corporate directory, without assigning permissions manually inside the platform.
By assigning security groups in Entra ID, your identity team can grant, change, and revoke Simetrik roles centrally, keeping your corporate directory as the single source of truth for identity management.
This mechanism is available to enterprise accounts that have been enabled for it. It's aimed at the identity and security teams responsible for administering your corporate directory.
How the integration works
Simetrik integrates with your corporate directory through a federated enterprise connection. The exchange happens during sign-in:
Sign-in
The user opens Simetrik and authenticates with their corporate credentials.
Groups are sent
Microsoft Entra ID reports the security groups the user belongs to.
Interpretation
Simetrik parses each valid group and resolves it to an account, workspace, and role.
Sync
The user's roles in Simetrik are updated based on the groups received.
On every sign-in, Simetrik recalculates the user's full set of roles from the groups it receives. This means a user's permissions in Simetrik always reflect the latest snapshot of the directory at the moment they authenticated.
Your directory is the source of truth. Once the integration is enabled, roles managed through this mechanism are administered exclusively from Microsoft Entra ID — no manual changes are required inside Simetrik.
Key concepts
| Concept | Description |
|---|---|
| Account | Your organization's space within Simetrik. Each account has a unique numeric identifier, provided by Simetrik. |
| Workspace | A workspace inside an account, where reconciliations and operational resources live. Identified by a numeric ID. |
| Role | The set of permissions a user has within a workspace (for example: supervisor, builder, operator, viewer). Each role has a unique identifier provided by Simetrik. |
| Security group | A Microsoft Entra ID group whose name encodes a combination of account, workspace, and role. A user's membership in the group determines the permissions they receive in Simetrik. |
Group naming convention
Each security group must be named following a convention made up of the SIMETRIK prefix and three components, separated by underscores:
SIMETRIK_{account_id}_{workspace_id}_{role_id}Example:
SIMETRIK_2045_310_9f2c41d8-3b6e-4a1f-8c2d-5e7a90b314f6| Component | Description | Origin |
|---|---|---|
SIMETRIK prefix | Identifies the group as belonging to the Simetrik integration. It makes governance and auditing of these groups easier, and guarantees that no unrelated corporate group is interpreted by the integration. | Fixed |
| Account ID | The numeric identifier of your organization's account in Simetrik. | Provided by Simetrik |
| Workspace ID | The numeric identifier of the workspace being granted access. | Provided by Simetrik |
| Role ID | The unique identifier of the role the user will have in that workspace. | Provided by Simetrik |
A few things to keep in mind about the format:
- The value can be sent as a single string (one group) or as an array (a list of groups) — both formats are accepted by the integration.
- A user can belong to multiple groups, receiving a different role in each workspace.
- Groups whose name doesn't follow the convention are ignored by the integration, without raising errors or affecting the rest.
- Only groups belonging to accounts that have been previously enabled by Simetrik are processed. Groups referencing other accounts are discarded.
Simetrik provides the catalog of identifiers (account, available workspaces, and roles) to your organization as part of the enablement process.
Example profile received by Simetrik
During authentication, the directory shares the user's profile with Simetrik. Security groups must arrive inside the groups attribute of that profile. Here's an illustrative example (with fictional data) of what that information looks like:
{
"name": "Jane Doe",
"email": "jane.doe@yourcompany.com",
"email_verified": true,
"identities": [
{
"provider": "waad",
"connection": "YourCompany",
"isSocial": false
}
],
"groups": [
"SIMETRIK_2045_310_9f2c41d8-3b6e-4a1f-8c2d-5e7a90b314f6",
"SIMETRIK_2045_312_4b8e23a7-6d91-4c05-9e3f-12c8d7a6450b",
"GRP_MFA_ENABLED",
"D_ADMIN_STAFF",
"S_CORPORATE_VPN_ACCESS"
]
}Only the groups attribute is read by the integration. From the example above, each entry is interpreted as follows:
| Group received | Result |
|---|---|
SIMETRIK_2045_310_9f2c41d8-…14f6 | Processed — role 9f2c41d8-…14f6 in workspace 310 of account 2045. |
SIMETRIK_2045_312_4b8e23a7-…450b | Processed — role 4b8e23a7-…450b in workspace 312 of the same account. |
GRP_MFA_ENABLED and other corporate groups | Ignored — they don't carry the SIMETRIK prefix or follow the convention; they don't raise errors or affect the processing of the rest. |
As shown above, your directory can send the user's full list of groups — including corporate groups unrelated to Simetrik — without risk: the integration only processes the ones that follow the convention and belong to enabled accounts.
Configuring Microsoft Entra ID
Setting this up on your side generally involves four steps:
Create the security groups
For every combination of workspace and role you want to manage, create a security group in Microsoft Entra ID whose name follows the convention described above.
Assign users to the groups
Add each user who should receive the corresponding role to the relevant group. Ongoing administration — onboarding, role changes, offboarding — is handled entirely by changing group membership.
Enable sending groups to Simetrik
Confirm that the enterprise application associated with Simetrik has group claims enabled, so the user's security groups are included in the profile shared during authentication. This step is validated together with the Simetrik team during enablement.
Validate the full cycle
Run a controlled test: assign a pilot user to a group, sign in to Simetrik, and confirm the role is granted correctly. Then remove the group and confirm the role is revoked on the next sign-in.
Supported operations
| Operation | How it's done | When it applies |
|---|---|---|
| Grant | Add the user to the corresponding security group. | On the user's next sign-in to Simetrik. |
| Modify | Change group membership (for example, remove the group for one role and add the group for another). | On the user's next sign-in to Simetrik. |
| Revoke | Remove the user from the security groups associated with Simetrik. | On the user's next sign-in to Simetrik (see Limitations). |
Limitations and considerations
Sync happens only at sign-in. Changes made in the directory don't propagate in real time. If a security group is removed from a user, they'll keep the associated role in Simetrik until their next sign-in, at which point the platform recalculates their permissions and applies the change.
- Deferred revocation — removing a role isn't immediate; it takes effect the next time the user authenticates. If you need to revoke access urgently, the recommended path is to block or disable the user in your own directory (which prevents new sign-ins), and notify Simetrik so active sessions can be closed if needed.
- Enabled accounts only — the integration only processes Simetrik accounts that have been agreed upon and enabled in advance. Adding new accounts requires coordination with Simetrik.
- Identifiers are managed by Simetrik — account, workspace, and role IDs are defined by Simetrik. Creating new workspaces or roles, and delivering their identifiers, is handled together with the Simetrik team.
- Strict format — group names that don't follow the convention are silently ignored. We recommend establishing an internal naming control when creating the groups.
Availability summary
| Capability | Availability |
|---|---|
| Granting roles per workspace via security groups | Available |
| Modifying roles by changing group membership | Available |
| Revoking roles when a group is removed (effective on the next sign-in) | Available |
| Assigning different roles per workspace for the same user | Available |
| Sending groups as a single string or as an array | Available |
| Real-time sync (without requiring a sign-in) | Not available |
| Immediate role revocation when a group is removed | Not available |
| Provisioning users who have never signed in | Not available |
Getting help
For the identifier catalog, enabling the integration, or any question about the behavior described in this guide, reach out to your Simetrik contact through your usual support channels.