What changed with Unified login settings in Engagement
Unified login introduces a clearer way to manage your Bloomreach settings by separating security and identity management from product configuration. Settings that previously lived under Account settings within Project settings have moved to Workspace settings and Administration section, creating a centralized approach to managing access across all your Bloomreach products.
Benefits of the new structure
The reorganized settings structure solves several challenges that existed when security and access management were tied to individual product instances:
Single source of truth for security
Security, SSO, user, and group management are now handled once at the organization or workspace level. This centralized approach makes audits and compliance easier—you can answer "who can access what?" from one location instead of checking multiple product instances.
Cleaner separation of concerns
Identity management (authentication, users, groups, SSO) is now distinct from product configuration (project variables, campaign settings, channel configuration). Security and unified login live in the workspace Security section, while product-specific settings remain at the project level where they belong.
Simplified user management
Adding or removing users and groups is centralized for all relevant modules, eliminating the need to update each instance separately. This streamlines both onboarding new team members and offboarding departing ones.
Better scalability across products
As Bloomreach adds more modules and features, they can plug into the same unified security layer without requiring separate login or role configurations for each one. Your security settings work consistently across Engagement, Data hub, Discovery, and future products.
Reduced duplication and inconsistencies
You no longer need to maintain slightly different user or role definitions across instances. This eliminates edge cases where a user might be removed from one product but still have access in another.
Settings location comparison
The following table shows where each setting appears in Unified login compared to the previous non-unified login structure:
| Setting category | What it manages | Non-unified login location | Unified login location | Access level |
|---|---|---|---|---|
| Domains | Custom tracking domains for your projects | Project settings > Account > General > Domain docs | Workspace settings > General > Domain docs | Workspace |
| Project variables | Account-level variables shared across projects | Project settings > Account > General > Project variables docs | Workspace settings > General > Project variables docs | Workspace |
| Groups | User groups for access management | Project settings > Account > Access management > Groups docs | Workspace settings > Access management > Groups docs | Workspace |
| Users | User accounts and basic information | Project settings > Account > Access management > Account team docs | Administration > Users > Users tab docs | Organization |
| Roles | Custom roles and permissions | Project settings > Account > Access management > Roles Roles | Administration > Users > Roles tab docs | Organization |
| Two-step verification | Multi-factor authentication settings | Project settings > Account > Security > Two-step verification (docs) | Administration > Settings > Security > Two-step verification | Organization |
| SSO | Single sign-on integration | Project settings > Account > Single sign-ondocs | Administration > Settings > Single sign-on docs | Organization |
| Project settings | Project-specific configuration (General, Terms & Conditions, Custom Tags, Access management, Security, Channels, etc.) | Project settings > Project section | Project settings > Project section | Project |
| Campaign settings | Campaign-specific configuration (General, Privacy management, Channels, Mapping, Evaluation) | Project settings > Campaigns section | Project settings > Campaigns section | Project |
Note
In the non-unified login setup, roles existed in two separate places (Account-level and Project-level). Unified login consolidates all role management into a single location in Administration, eliminating duplication and simplifying role administration.
Understanding the new settings hierarchy
Settings are now organized into three levels based on their scope:
Workspace-level settings apply across all projects in your workspace:
- Domains
- Project variables (shared across projects)
- Groups
Organization-level settings apply across all Bloomreach products:
- Users
- Roles (consolidated from both Account and Project levels)
- Two-step verification
- Single sign-on (SSO)
Project-level settings remain specific to individual projects:
- Project configuration (General, Terms & Conditions, Custom Tags, project-specific variables, Access management including API, Security, Performance dashboards, Loomi, Discovery integration)
- Campaign configuration (General, Privacy management, Channels, Mapping, Evaluation)
Note
API functionality in Engagement remains in Project settings > Project > Access management > API and hasn't moved to Workspace settings. The Workspace-level API configuration serves a different purpose for workspace-wide integrations.
How to access your settings
Access Workspace settings
- Log in to your Engagement or Data hub instance.
- Click the settings icon (gear symbol) in the top right corner of the interface.
- Select Workspace settings from the dropdown menu.
- Navigate to the relevant section (General or Access management) in the left sidebar.
Access Administration settings
- Log in to your Bloomreach account.
- Click the settings icon (gear symbol) in the top right corner.
- Select Administration from the navigation options.
- Choose between Users or Settings sections depending on what you need to configure.
Access Project settings
- Log in to your Engagement or Data hub instance.
- Click the settings icon (gear symbol) in the top right corner.
- Select Project settings from the dropdown menu.
- Navigate through the Project or Campaigns sections in the left sidebar to find your desired settings.To run code, enable code execution and file creation in Settings > Capabilities.
Updated 7 days ago