Table of Contents SCIM User Lifecycle SCIM controls workspace enrollment while preserving the global Diggle account. Provision The provider assigns the user and sends POST /Users with an approved email-shaped userName. Diggle creates or correlates the account and establishes the managed workspace relationship. An approved workspace email domain or existing
Table of Contents Workspace API Procedures Use these procedures to manage projects and workspace users. Procedure Purpose createProject Create a project. deleteProject Archive a project, or permanently delete it when explicitly requested. upsertWorkspaceUser Create or update a workspace user; optionally assign projects. getWorkspaceUsers List workspace users. getWorkspaceUser Look up a
Table of Contents Workspace API Authentication Create a Workspace API key after Diggle enables Workspace API for the selected workspace. Enable access and create a key Ask Diggle to enable Workspace API for the workspace. The Workspace API card offers Contact Diggle when it is not enabled. As a workspace
Table of Contents Set Up SCIM Provisioning Provision and manage workspace users using SCIM 2.0. SCIM manages workspace enrollment, roles and the provisioning source’s user profile; SSO authenticates the global Diggle account. Enable SCIM separately from Workspace API and SSO. Create a provisioning token Ask Diggle to enable SCIM provisioning
Table of Contents API & SCIM Errors Workspace API and SCIM use different error formats. Check both the HTTP status and the returned body. Workspace API Procedure errors are plain text. The dispatcher returns an explicit procedure error status where one is assigned; otherwise it returns 500. The older project
Table of Contents Enterprise Access and Licensing Effective Enterprise workspace access replaces personal paid entitlement. When Enterprise access starts A qualifying admin, creator or runner membership in an active workspace with applicable company access grants Enterprise access. Local blocking and SCIM source deactivation prevent qualification. A pending invitation alone does
Table of Contents Workspace Roles and Access Workspace role values used by integrations map to Diggle’s user-facing roles. API / SCIM value Diggle terminology Purpose admin Admin Manage workspace users and settings; access all workspace projects and administer project access. creator Author Create projects and content; edit content where project
Table of Contents Microsoft Entra SSO Microsoft Entra SSO authenticates users; SCIM provisioning manages workspace access. They are separate capabilities. Before you start Ask your workspace administrator to confirm that Microsoft sign-in is available for your organization and that your Diggle workspace access is ready. Use the intended work Microsoft
Table of Contents SCIM User Reference Reference for Diggle’s supported SCIM User attributes and update behavior. All calls require a Bearer provisioning token and are scoped to its workspace and provisioning source. User representation { “schemas”: [ “urn:ietf:params:scim:schemas:core:2.0:User”, “urn:ietf:params:scim:schemas:extension:diggle:2.0:User” ], “id”: “<scim-user-id>”, “userName”: “[email protected]”, “emails”: [ { “value”: “[email protected]”, “type”:
Table of Contents Configure Microsoft Entra SCIM Provisioning Configure Microsoft Entra outbound User provisioning for Diggle’s supported SCIM subset. Before you start You need Diggle workspace administrator access, an Entra administrator who can manage application provisioning, the Entra tenant ID, and one assigned test user with an approved work email.
