architect-auth-scim

Manage Braze SDK authentication keys and provision dashboard users via SCIM endpoints.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-auth-scim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-auth-scim
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/architect-auth-scim
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-auth-scim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organizations need a repeatable, secure way to manage client-side SDK authentication keys and to automate dashboard user onboarding/offboarding; manual dashboard workflows are error-prone, slow, and create audit gaps. This Skill centralizes the procedures and reference details required to rotate SDK keys safely, inspect active keys, and provision or modify dashboard users via SCIM APIs.

Core Features & Use Cases

  • Safe SDK key lifecycle: step-by-step pattern for creating a secondary key, promoting it to primary, and deleting the old key to enable zero-downtime rotation.
  • SCIM provisioning automation: create, search, update (PUT full-permission replacement), and delete dashboard users programmatically with SCIM tokens and required headers.
  • Permission hygiene & least privilege: guidance on granular vs legacy SCIM permission models and warnings about PUT semantics that can unintentionally remove permissions.
  • Use case: Automate onboarding for a new engineering team by creating users, assigning workspace and team permissions, and rotating app SDK keys as part of CI-driven deployments.

Quick Start

Provision a dashboard user via SCIM and perform a safe SDK authentication key rotation for the target app using a valid SCIM token and the X-Request-Origin header.

Frequently Asked Questions about architect-auth-scim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate SCIM user provisioning for a Braze dashboard?

Automate SCIM user provisioning by using SCIM API endpoints to programmatically create, search, update, and delete dashboard users with valid Bearer SCIM tokens and the required X-Request-Origin header.

What is the safest way to rotate SDK authentication keys without downtime?

Safe SDK key rotation involves creating a secondary key, promoting it to primary, and then deleting the old key. This pattern ensures zero-downtime rotation during CI-driven deployments or manual lifecycle management.

Do I need specific headers and parameters to manage SDK keys via API?

Yes, managing SDK keys requires Bearer SCIM tokens, the X-Request-Origin header, and specific app_id and key_id parameters for the SDK endpoints to authenticate and target the correct workspace application.

Why does updating SCIM users with PUT requests require caution?

Updating SCIM users with PUT requests requires caution because strict PUT semantics enforce full-permission replacement, which can unintentionally remove existing permissions if the request body does not include the complete permission set.

Can I automate onboarding engineering teams by assigning workspace and team permissions?

Yes, you can automate team onboarding by creating users via SCIM, assigning granular workspace and team permissions, and rotating app SDK keys as part of automated CI-driven deployment workflows.

What distinguishes granular SCIM permissions from legacy models?

Granular SCIM permissions provide more specific access control compared to legacy models, enabling better least privilege hygiene when provisioning dashboard users and managing workspace security boundaries.