LogoLogo
Get support
  • Home
  • Make API
  • Make Bridge
  • White Label
  • MCP Server
  • Make White Label
  • Release notes
    • Release 2025.03
    • Release 2025.02
    • Release 2025.01
    • Release 2024.13
    • Release 2024.12
    • Release 2024.11
    • Release 2024.10
    • Release 2024.09
    • Release 2024.08
    • Release 2024.07
    • Release 2024.06
    • Release 2024.05
    • Release 2024.04
    • Release 2024.03
    • Release 2024.02
    • Release 2024.01
  • Install and configure apps
    • Native apps
      • App versions
      • App tiers
      • Uninstall native apps
    • Custom apps
      • Sharing with a link
      • Compiling the app
    • OAuth 2.0 setup
      • Configure access for end-users
      • Alternate option: require user-provided credentials
    • App timeout
      • Native apps
      • Custom Apps
    • Shared webhooks
    • Preinstalled tools
    • Manage custom apps
      • Managing access to custom apps
      • Custom app creation flow for administrators
      • Versioning and maintenance
    • Google
      • Steps in Google Developer Console
      • Steps in Make
      • Connection and scope reference
    • Microsoft
      • Steps in Azure portal
      • Steps in Make
      • Connections and permission reference
    • Facebook and other Meta apps
      • Steps on the Meta for Developers portal
      • Steps in Make
      • Connection and scope reference
    • Discord
      • Steps in Discord
      • Steps in Make
    • Asana OAuth credentials
      • Steps in Asana
      • Steps in Make
    • ClickUp OAuth credentials
      • Steps in ClickUp
      • Steps in Make
    • Configure the module Email > Send an Email to a Team Member
    • Verification
  • Manage login
    • Configure Single Sign-on
      • Configure single sign-on using OAuth 2.0 or SAML 2.0
      • Example: Setting up single sign-on with MS Azure Active DirectoryPage 1
      • Logging in using SSO
    • Configure two-factor authentication
    • Instance level roles
      • Admin - system roles
      • Admin - developer roles
      • Admin - support roles
    • Okta SAML
      • Configuration steps
      • Steps on Okta
      • Steps on Make
      • Service provider initiated SSO
      • Troubleshooting
  • Audit activity
    • Access recent executions
      • Search scenario executions
      • Access scenario execution information
      • Access a scenario's execution log
      • Unlock a scenario execution
    • View recently created scenarios
      • Access scenario information
    • Log out a user's current session
    • Organization's operations, data transfer, and storage usage
  • Manage the end-user life cycle
    • Provision new users
      • Create users and organizations
      • Define the organization's license
      • User roles and access management
    • Maintain end users
      • Manage apps and features options
    • Deprovisioning
  • Manage organizations and teams
    • Creating organizations
    • Create and add new users to organizations
    • Organization roles
    • Remove a user from an organization
    • Transfer organization ownership
    • Delete an organization
    • Manage instance-level user access roles
      • Assign user roles
      • Customize user roles
    • Add users to organizations via an email invitation
    • Default organizations permissions
    • Default team permissions
  • Customize your instance
    • General procedure for configuring system settings
    • Rebrand your instance
    • Customize user access to features
    • Configure token access with 3rd parties
    • Custom domains
      • Requirements
      • General process
      • Base and primary domains
      • Migration of SSO
      • App OAuth redirect URIs
      • Custom code injection
        • Dynamic CSPs
  • Configure JWT authorization
    • Enable JWT authorization
      • Mapping
Powered by GitBook

Resources

  • Academy
  • Community
  • Help Center

Useful links

  • Support
  • Privacy Notice
  • Status Page
  • make.com

Follow us

  • LinkedIn
  • X (Twitter)
  • Facebook
  • Instagram

© 2025 make.com

On this page
Export as PDF
  1. Manage the end-user life cycle

Deprovisioning

When you need to deprovision a customer from your instance, using Make API allows you to automate the process and offers more functionality than the Administration interface. The recommended procedure is to set all consumables to 0 and give the customer limited access to the organization. This way preserves their scenarios and data in the event that the customer decides to subscribe again.

  1. Use the license object to set operations and other consumables to 0 or the minimum value. This configuration freezes the organization and its scenarios while allowing former customers to have access to their data stores and other assets associated with their organization.

  2. Transfer organization ownership to a dummy owner that you create. Reassign the end user to a role with limited access, such as member. This step limits the former customer's permission privileges while preserving their data and other assets for later use if the customer returns.

You can verify the deprovisioned user's access by using the Login as user feature on Administration > Users > Detail.

Once you click Login as user, you immediately see that user's dashboard. You can edit the deprovisioned user's notification settings so they do not receive notification emails.

To return to Administration, you need to log out as the user and then log in with your credentials.

PreviousManage apps and features optionsNextManage organizations and teams

Last updated 4 months ago