Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.provisionr.io/llms.txt

Use this file to discover all available pages before exploring further.

It is unlikely to see anything on this list be released in the next 6 months. We’d love to hear from you if you have a compelling use case so we can re-evaluate whether it makes sense to build. Please see our release to learn more about what we’re working on next. See our focus areas to understand where we are focusing our efforts.

​
Directory Identity and HRIS Data

  • Auth0 / Okta Customer Identity
  • BambooHR (HRIS)
  • Clerk
  • Gusto (HRIS)
  • Microsoft Entra ID (formerly Azure AD)
  • OneLogin
  • Ping Identity
  • Propel Auth
  • Rippling (HRIS)
  • SalesForce
  • Workday (HRIS)
  • (Suggest other providers)

​
Group and Resource Vendors

  • AWS IAM Groups (recommend using Identity Center instead)
  • GitHub organization members
  • GitHub project members
  • Microsoft Entra (formerly Azure AD) Groups
  • SalesForce
  • (Suggest other providers)

​
MDM Integrations

Our Workspace CLI client sends device metadata to the server. In the future, we could use that data to check if a device is not up-to-date with the latest versions or configurations and revoke tokens. We could also extend that functionality to perform API calls to MDM providers to get the latest device metadata from the last check in, and revoke access to sensitive groups and resources if they no longer meet device trust standards.
  • Jamf
  • Kandji
  • Mosyle
  • (Suggest other providers)

​
No Code Workflows

We know that most IT teams rely on low/no code workflows. We have native support for inbound and outbound webhooks that provide minimum viable functionality. We are going to integrate with Zapier as our first vendor for an enhanced experience. Depending on complexity, customer demand, and ecosystem fit, we are interested in adding support for additional vendors.
  • n8n
  • Okta Workflows
  • Slack app, bot, and slash command workflows
  • Tines
  • Workato
  • (Suggest other providers)

​
ITSM and Ticket Workflows

We assume that most teams are using helpdesk ticket software. Every team has a different workflow and we are in the early research phase for how we can create a generic approach to integrate with ticket software, and what value that would offer. Please reach out with your thoughts and use case to help us learn more. For the time being, we are building the Approval Control module that will provide self-service access requests and visibility into what access each user already has. You can use canned responses, chat bots, or knowledge base articles to link users to the self-service portal.
  • FreshDesk
  • FreshService
  • GitHub Issues
  • GitLab Issues
  • JIRA Issues
  • JIRA Service Management
  • ServiceNow
  • Slack Bot and Slash Command Workflows
  • Zendesk
  • (Suggest other providers)

​
GRC and IGA Integrations

We believe that one size rarely fits all use cases, and you might have multiple vendors that cover all of your identity and access management (IAM), governance, risk and compliance (GRC), and identity governance and administration (IGA) needs. It’s a common perception that you would use Provisionr for baseline (job-role) entitlement provisioning, and use your existing vendor for access requests that might use API calls back to Provisionr to add the user to the policy, or manage the requests independently if not using authoritative rulesets. We want to play well with others and allow you to integrate your workflows and vendors seamlessly.
  • ConductorOne
  • Lumos
  • Okta Identity Governance (OIG)
  • Veza
  • (Suggest other small/mid-market providers)