Deployment model

Every organization is different, which means that as part of every deployment, Oblique needs to be customized to your organization’s needs. We will work with you to help define a deployment plan that is tailored to your organization’s needs.

Oblique deployments typically follow a phased approach: first, data validation; then, a pilot test with a limited team; and finally, an organization-wide rollout.

Defining your goals, success criteria, and stakeholders

Prior to deploying Oblique, we recommend aligning on your organization’s goals, success criteria, and key stakeholders.

Example goals

Simplify access management: Generate and manage attribute-based and cross-functional groups automatically across multiple systems
Enable access self-governance: Allow teams to request and approve access and team changes independently, within security guardrails
Reduce time spent on access management: Automate access management and reduce the time spent by IT and security teams on manual access changes
Establish single source of truth for authorization: Create one place to understand who has access to what across the organization

Example success criteria

Reduce access request tickets by XX%
Reduce time spent by IT and security teams on manual access changes by XX%
Reach XX% user satisfaction with self-service access management

Example stakeholders

Project lead: Primary technical contact responsible for main deployment decisions and day-to-day operations
IT and Security teams: Help refine access requirements, learn how to use Oblique, participate in pilot testing, and provide feedback
HR contact: Helps validate employee data quality and attribute mapping from HRIS systems
Engineering lead: Helps define initial cross-functional teams
Executive sponsor: Provides organizational alignment to prioritize the project and has decision-making authority for the deployment

Deployment phases

Phase 1: Data validation and initial groups

The goal of this phase is to import the data that Oblique will use to manage access, and validate and improve data quality.

Connect Oblique (in read-only mode) to existing user and user attribute sources, such as an identity provider and HRIS
Establish requirements for team structures and access requests, such as naming conventions, ownership, and approval requirements
Create initial attribute-based and team groups
Review data quality of current users, attributes, and groups, and identify and address missing or incorrect data

Phase 2: Pilot test

The goal of this phase is to validate Oblique works for your organization, for both admins and through self-service workflows. This is typically done with a limited group of users.

Begin pushing access changes from Oblique to integrations
Establish support channels and feedback processes
Deploy self-service functionality to pilot teams
Test self-service workflows for access requests and team membership changes

Phase 3: Organization-wide rollout

The goal of this phase is to successfully deploy Oblique organization-wide.

Communicate rollout across the organization, with training materials including videos, documentation, and FAQs
Enable all employees to request access and team changes
Measure success criteria

Support structure

As part of a deployment, Oblique typically provides the following support:

Joint Slack channel for ongoing support and questions
Regular sync meetings to talk live and address any issues that arise
Training materials customized for your organization

Rollback plan

If Oblique doesn’t work for your organization or the deployment doesn’t meet success criteria, we will work with you to address the issue, or if that’s not possible, roll back the use of Oblique.

This typically involves:

Pausing syncing and removing integrations from Oblique, so that existing access controls at the point of being paused remain in place
Exporting your organization’s configuration as code, so that you can use the groups, teams, and requirements you’ve already defined elsewhere
Deleting your data from Oblique