Skip to main content

Deciding which features to implement

Use the guidance below to map business requirements to Bravura Identity capabilities. Focus on the minimal viable deployment first, then expand modules in phases.

Table 1. Decision framework

Primary goal

Recommended features

Automate onboarding and offboarding

Automated Provisioning, SoR integration, connectors to AD/Exchange/SaaS

Enable delegated requests and approvals

Request Portal, Workflow & Authorization, Delegated Admin

Reduce privileged account sprawl

Role model (RBAC), Credential Vault integration, PAM

Meet compliance / certification

Access Certification, Audit Logging, Reports & Dashboards

Detect orphan/dormant accounts

Auto-Discovery, Identity Synchronization

Support complex fulfilment (legacy apps)

Human Implementer Fulfillment workflows



Feature selection matrix

Assess features as Required, Recommended, or Situational.

Feature

Description

When to Implement

Priority

Automated provisioning

SoR-driven account lifecycle automation

Always recommended for onboarding/offboarding

Required

Request portal

Self-service and delegated requests

When managers/business owners request access on behalf of staff

Required

Workflow Manager

Validations, approvals, escalations

Core to request handling

Required

Access Certification

Periodic review by business owners

Regulated environments; audit readiness

Recommended

RBAC (Roles)

Role templates, auto-assignment

Organizations with repeatable access patterns

Recommended

Segregation of Duties (SoD)

Conflict detection/prevention

Finance, HR, or regulated departments

Recommended

Auto discovery

Inventory and detect orphan/dormant accounts

Multi-system environments

Required

Human implementer fulfillment

Manual completion for legacy systems

When connectors are not feasible

Situational

Physical asset tracking

Badges, tokens, asset lifecycle

Organizations that manage physical credentials

Situational

Deployment patterns

  • Baseline: Provisioning + Request Portal + Workflow + Auto discovery.

  • Compliance-focused: Baseline + Access certification + SoD + Reports.

  • Hybrid / Legacy-heavy: Baseline + Human fulfillment + extensive connectors.

  • Rapid start (Bravura Workforce Pattern): Use preconfigured Bravura Workforce Pattern to accelerate rollout.

Questions to confirm before rollout

  1. Which systems will act as System-of-Record (HR, contractor DB)?

  2. Which connectors are required for inbound discovery and outbound provisioning?

  3. Who are the business owners for certification scopes?

  4. Are there legacy systems requiring manual fulfillment?

  5. What are audit and retention policy requirements?