The ORGADMIN role in Snowflake is responsible for managing organization-level administrative functions, which include managing billing and credit data. This role has the highest level of administrative privileges and can oversee multiple Snowflake accounts within an organization.
Snowflake Documentation: Account and Organization Roles

Details around the privileges that have been granted for all objects in an account.
TheACCESS_HISTORYview in Snowflake provides a comprehensive log of access control changes, including grants and revocations of privileges on all securable objects within the account. This information is crucial for auditing and monitoring the security posture of your Snowflake environment.
Here ' s how to understand and use theACCESS_HISTORYview:
Purpose of ACCESS_HISTORY View:It is designed to track changes in access controls, such as when a user or role is granted or revoked privileges on various Snowflake objects. This includes tables, schemas, databases, and more.
Querying ACCESS_HISTORY:To access this view, you can use the following SQL query pattern:
SELECT*FROMSNOWFLAKE.ACCOUNT_USAGE.ACCESS_HISTORYWHEREEVENT_TYPE = '
GRANT ' OREVENT_TYPE = ' REVOKE ' ;
Interpreting the Results:The results from theACCESS_HISTORYview include the object type, the specific privilege granted or revoked, the grantee (who received or lost the privilege), and the timestamp of the event.
This data is invaluable for audits and compliance checks.
Reference:For detailed information on theACCESS_HISTORYview and how to interpret its data, please visit the official Snowflake documentation: https://docs.snowflake.com/en/sql-reference/account-usage
/access_history.html

A materialized view in Snowflake gets suspended when structural changes that could impact the view's integrity are made to the base table, such as B. When a column is dropped from the base table. Dropping a column from the base table on which a materialized view is defined can invalidate the view's data, as the view might rely on the column that is being removed. To maintain data consistency and prevent the materialized view from serving stale or incorrect data, Snowflake automatically suspends the materialized view.
Upon suspension, the materialized view does not reflect changes to the base table until it is refreshed or re-created. This ensures that only accurate and current data is presented to users querying the materialized view.
References:
Snowflake Documentation on Materialized Views: Materialized Views