Snowflake Security, RBAC, and User Administration · Topic 5 of 16
Future Grants, Managed Access Schemas, Cloned Objects and Warehouse Grants
Implement future grants and managed access schemas, understand how cloning affects granted privileges, and manage warehouse privileges in Snowflake.
- 4 min
- Schema level future grants take precedence over database level ones.
- Future grants need MANAGE GRANTS (or the schema owner in a managed schema).
- Managed access: only the schema owner or MANAGE GRANTS roles grant; object owners cannot.
What it is
Four features decide how privileges behave as objects come and go. Future grants give privileges on objects that do not exist yet. Managed access schemas take grant decisions away from object owners. Cloning creates new objects, and the clone may or may not carry the grants of the source. Warehouse privileges control who can use, run and resize compute.
How it works
Future grants
GRANT SELECT ON FUTURE TABLES IN SCHEMA sales.public TO ROLE sales_ro;
GRANT USAGE ON FUTURE SCHEMAS IN DATABASE sales TO ROLE sales_ro;
SHOW FUTURE GRANTS IN SCHEMA sales.public;
REVOKE SELECT ON FUTURE TABLES IN SCHEMA sales.public FROM ROLE sales_ro;
Rules and restrictions to know:
- Precedence: if future grants for the same object type exist at both database and schema level, the schema level grants win and the database level grants for that type are ignored. This holds even when the grants go to different roles.
- Who can define them: at database level and for standard schemas, the global
MANAGE GRANTSprivilege (SECURITYADMIN and ACCOUNTADMIN by default). In a managed access schema the schema owner can also do it. - Not retroactive: revoking a future grant keeps the privileges already given on existing objects.
- Not applied when a table is renamed or swapped.
- Only one future
OWNERSHIPgrant is allowed per object type. - Future grants cannot be defined for some objects, including tags and policy types such as masking and row access policies.
A scenario with a database level future grant that "stopped working" in one schema usually has a schema level future grant for the same object type. The schema level one replaced it.
Managed access schemas
In a regular schema the owner of an object can grant privileges on it (DAC). In a managed access schema the object owner loses that power. Only the schema owner or a role with MANAGE GRANTS can grant privileges on objects there, including future grants.
CREATE SCHEMA finance.reports WITH MANAGED ACCESS;
ALTER SCHEMA finance.old_schema ENABLE MANAGED ACCESS;
ALTER SCHEMA finance.old_schema DISABLE MANAGED ACCESS;
Object owners can still create and own objects; they just cannot hand out access. Use it when a central team must control all grants and still let delivery teams build. A future OWNERSHIP grant in a managed schema can go only to a subordinate role of the schema owner.
Cloned objects and granted privileges
A clone is a new object. The docs describe how privileges behave:
| Case | Result |
|---|---|
Clone without COPY GRANTS | Explicit privileges on the source are not copied; the clone gets the future grants defined for that object type in the schema |
Clone with COPY GRANTS | The clone gets the explicit privileges of the source, but not future grants |
| Clone of a database or schema | Child objects keep the privileges granted on them; the container clone itself does not inherit grants of the source |
| Database roles | Cloned only when the whole database is cloned |
CREATE TABLE sales.public.orders_dev CLONE sales.public.orders COPY GRANTS;
The role creating the clone needs privileges on the source and on the target containers, and owns the new object. Cloning a database also clones its database roles; cloning a single schema or table does not.
When a cloned table must keep the same readers, use COPY GRANTS. When it should follow the policy for new objects, clone without it and rely on future grants.
Warehouse grants
| Privilege | Allows |
|---|---|
| USAGE | Use the warehouse and run queries on it |
| OPERATE | Start, stop, suspend and resume it, and abort running queries |
| MODIFY | Change properties, including size |
| MONITOR | View queries and usage |
| OWNERSHIP | Full control, including grants |
MANAGE WAREHOUSES is an account level privilege equal to MODIFY, MONITOR and OPERATE on all warehouses. Separate duties by role: analysts get USAGE; a platform role gets OPERATE and MONITOR; only the owner team gets MODIFY.
GRANT USAGE ON WAREHOUSE reporting_wh TO ROLE analyst;
GRANT OPERATE, MONITOR ON WAREHOUSE reporting_wh TO ROLE platform_ops;
Common mistakes
Assuming a clone copies grants. It does not unless COPY GRANTS is used.
Mixing database and schema level future grants. The schema level grant overrides the database one for that object type.
Relying on future grants after a table swap or rename. They are not reapplied.
Giving MODIFY to everyone who runs queries. USAGE is enough to query; MODIFY allows resizing.
What to remember for the exam
- Schema level future grants take precedence over database level ones.
- Future grants need MANAGE GRANTS (or the schema owner in a managed schema).
- Managed access: only the schema owner or MANAGE GRANTS roles grant; object owners cannot.
- Clones start without the source's explicit grants unless COPY GRANTS is used.
- Warehouse: USAGE runs queries, OPERATE controls state, MODIFY changes properties, MONITOR views.
Check yourself
A table in a managed access schema is owned by a developer role. Can the developer grant SELECT on it?
No, only the schema owner or a role with MANAGE GRANTS can.
How can a cloned table keep its source's privileges?
Clone it with
COPY GRANTS.Which privilege lets a role resize a warehouse?
MODIFY (or MANAGE WAREHOUSES).
Topic 5 of 16 in Snowflake Security, RBAC, and User Administration
Test yourself on Snowflake Security, RBAC, and User Administration
The full Snowflake ADA-C02 question bank has 814 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.