Getting Started

Overview

This guide walks you through connecting a ServiceNow instance to Britive and granting your first just-in-time access session to a ServiceNow role — with no permanently assigned admin roles and full audit logging on every checkout.

What you’ll accomplish:

• Create a Britive integration user in ServiceNow with the required API permissions
• Onboard the ServiceNow application in the Britive console
• Create an access profile for a ServiceNow role
• Check out and verify JIT access end-to-end

Prerequisites

Before you begin, make sure you have:

• A Britive tenant with administrator access
• ServiceNow Administrator access to create users and manage roles
• A ServiceNow instance (production or PDI)

How It Works

Britive uses the ServiceNow REST API (Table API) to manage role assignments on users. At checkout, Britive adds the target role to the requesting user’s account. At checkin (or on expiry), the role is removed — no standing elevated roles remain on the account.

User → Britive Console → ServiceNow Table API → User Role Assignment (add/remove)

Onboarding the Application

Connect your ServiceNow instance to your Britive tenant. This is a one-time setup performed by an administrator.

export SN_INSTANCE_URL=https://yourinstance.service-now.com
export SN_ADMIN_USER=britive_integration
export SN_ADMIN_PASSWORD=...   # From Britive Secrets Store
export BRITIVE_TENANT=your-tenant
export BRITIVE_API_TOKEN=your-token

data "britive_application" "servicenow" {
  name = "ServiceNow"
}

Create Your First Access Profile

data "britive_application" "servicenow" {
  name = "ServiceNow"
}

resource "britive_profile" "sn_change" {
  app_container_id    = data.britive_application.servicenow.id
  name                = "SN-ChangeManager"
  expiration_duration = "4h0m0s"

  associations {
    type  = "Environment"
    value = "your-servicenow-instance"
  }
}

Verify

Troubleshoot

Next Steps

• Britive documentation