How to Configure Make SQL Server Permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up make sql server permissions, create a dedicated database user for your automation scenarios. Next, grant that user only the exact table rights needed to run each step. Many teams take a shortcut and use a shared admin account to get workflows running fast. This broad setup creates big risks when an automated step runs a bad query. A single mistake in a scenario can alter or delete production rows across the whole database. How make sql server permissions work In SQL Server, a databa

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

To set up make sql server permissions, create a dedicated database user for your automation scenarios. Next, grant that user only the exact table rights needed to run each step. Many teams take a shortcut and use a shared admin account to get workflows running fast. This broad setup creates big risks when an automated step runs a bad query. A single mistake in a scenario can alter or delete production rows across the whole database.

How make sql server permissions work

In SQL Server, a database user is the identity of a login inside a database. When an app needs to reach many databases, teams often create a standard SQL login. This login lives in the master database and maps to users in target databases. If Make only needs one database, you can use a contained database user instead. This user has its own password and does not need a login in master. First, an admin must turn on contained databases on the server and target database.

Once the user exists, you must decide what data it can read or write. SQL Server includes fixed database roles that group common rights together. You cannot change the permissions assigned to these fixed database roles. For example, the db_datareader role lets a user read all user tables and views. The db_datawriter role lets a user add, change, or delete data in all user tables. Avoid the db_owner role for automation. Members of db_owner can run all maintenance tasks and even drop the whole database.

If a workflow only needs a few tables, fixed roles are still too broad. Instead, keep the user in the basic public role, which already includes connect rights. Then grant select, insert, or update rights on the exact tables the scenario uses. You can also use db_denydatareader or db_denydatawriter to block reads or writes across user tables.

What native roles solve and what they miss

Native database roles and table grants control who can log in and touch specific objects. They stop a read-only Make scenario from dropping a table or changing billing records. Setting up a dedicated user for Make also helps you spot automation traffic in server logs. This basic setup is a vital first step for any production database.

Still, static database roles only check access at the object level. They do not inspect what individual queries do in flight during an active session. If a user has read rights on a customer table, it can pull every column by default. Native roles will not rewrite sensitive fields like emails, phone numbers, or card numbers in results. Similarly, a user with write rights can delete all rows in an allowed table at once by default. Static permissions also require you to store long-lived passwords inside your Make account settings.

Kubernetes API Server Access + AI Agent Permissions: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Steps to tighten automation database access

Start by listing every query your Make scenarios run against your SQL Server instance. Group these tasks into read-only jobs and jobs that must write or update rows. Create separate SQL users for read tasks and write tasks so most scenarios stay read-only. Never share human admin accounts with automated workflows.

Next, replace broad role memberships like db_datareader with table-level or view-level grants. Create custom SQL views that leave out columns holding national IDs, emails, or phone numbers. Grant your Make database user read access only to those safe views. Finally, review your active database users each quarter and remove old accounts that scenarios no longer use.

Add runtime guardrails beside SQL Server

Role grants and network rules are needed setup for SQL Server. Still, an allowed user or agent tool can send a bad delete or read raw customer fields over a valid session. In practice, hoop.dev runs beside the database as a sidecar for your SQL Server and checks TDS traffic without changing how clients log in.

With hoop.dev SQL Server controls, rules refuse banned statements before they run and can hold risky queries for human review. Matched sensitive values in supported result columns are masked before they reach the client. Furthermore, hoop.dev holds SOC 2 Type II and generates evidence for HIPAA, PCI DSS, SOX, and GDPR audits. See the source on GitHub.

Frequently asked questions

Should I give Make the db_owner role in SQL Server?

No, you should never assign the db_owner role to an automation tool. That role allows full control over the database and can even drop the database.

What is the difference between a SQL login and a contained database user?

A standard SQL login lives in the master database and can link to many databases. A contained user stays inside one database with its own password and no master login.

Can I change the permissions inside the db_datareader role?

No, SQL Server does not let you change the permissions of fixed database roles. To limit access to specific tables, create a custom role or grant table rights directly.

The query runs. The emails stay hidden.