All use cases

Enforce Chrome Password and Card Autofill Controls

This automation creates and deploys a macOS configuration profile that disables Chrome's password manager and credit card autofill features. It handles authentication, generates the required unique identifiers, and applies the policy automatically across the defined device and user scope.

Technical Automation

Process Automation

Configuration

Access Control

Trigger

A request to execute the workflow initiates the process of creating the Chrome security configuration profile.

Outcome

A non-removable macOS configuration profile is created for automatic deployment with Chrome password manager and credit card autofill disabled.

Trigger

A request to execute the workflow initiates the process of creating the Chrome security configuration profile.

Outcome

A non-removable macOS configuration profile is created for automatic deployment with Chrome password manager and credit card autofill disabled.

Before

An administrator would likely obtain an authentication token, generate unique profile identifiers, and assemble the macOS configuration profile manually. They would then submit the profile through the device management platform and configure its installation and scope settings.

How it works

Authenticate the workflow so it can submit a configuration profile to the device management environment.
Generate unique identifiers and build the predefined macOS profile that disables Chrome password management and credit card autofill.
Create the profile with automatic installation, user removal blocked, and the configured computer and user scope.

Workflow details

Authentication: The workflow first obtains a bearer token so the subsequent profile-creation request can be authorized in the device management environment.
Identifier generation: It creates two unique UUID v4 values for the configuration profile and its embedded payload, preventing the need to create these identifiers manually.
Policy construction: The workflow assembles a predefined macOS configuration profile that forces Chrome's password manager and credit card autofill settings to disabled.
Deployment settings: The profile is configured for automatic installation at the computer level, cannot be removed by users, and is scoped to all computers and JSS users defined in the request.
Operational result: The completed profile is submitted for creation in the device management platform, making the browser restrictions available for managed macOS systems without manual XML construction or profile setup.

What changed

Profile creation becomes a repeatable automated handoff: authentication, identifier generation, policy construction, installation settings, and scope are handled in one run, leaving administrators with the resulting managed profile instead of a manually assembled submission.

Work removed

Manually requesting an authentication token, generating profile and payload UUIDs, composing the XML configuration, entering Chrome policy settings, and submitting the profile for deployment.

Expected outcome

Each run can remove at least five recurring setup actions and produce one consistently configured Chrome restriction profile for managed macOS systems.

Connected tools

Jamf - Jamf Pro

Mindflow HTTP

Related flows

All use cases

Explore more workflows with similar topics or tools.

Automated Employee Offboarding

Automates employee offboarding by identifying recently changed employee records, checking whether offboarding is due today, removing qualifying users from Slack, suspending their Google Workspace and Okta access, and sending a detailed status email. This replaces a multi-system manual checklist with a consistent automated sequence.

Explore use case

Automated Background Check Evidence Collection

This automation identifies personnel records in Drata that do not have background check evidence and adds the available evidence to those records. It replaces repeated compliance lookups and uploads with a structured process that supports regulatory readiness.

Explore use case

Approval-Based Stale Access Key Governance

This automation identifies active IAM access keys that have not been used for more than 90 days, gathers the related user and issue evidence, and creates a trackable incident for review. It gives the responder a clear choice to deactivate the key or ignore the issue, then records the decision and closes the incident.

Explore use case

Less busywork. More possibility.

Let your agents handle the routine. Make room for what comes next.

Let’s talk