Knowing whether you need to request access
Learn to tell when you can already query data and when you need to bring in an access manager.
When to use this
- Use it before opening an access request.
- Use it when the table appears but the query fails.
- Use it when you need to explain to the manager exactly what is missing.
Before you start
- Find the table in the Data Catalog.
- Try a simple preview in QueryMesh Explorer, if that screen is available to you.
- Have a business justification for the access.
Step by step
- Confirm you can see the catalog and the schema.
- Confirm the table appears in the tree or in search.
- Try querying a few columns and a few rows.
- If access denied appears, read the message.
- Put the request together with the catalog, schema, table, purpose, and the duration you want.
- Send it to the access manager, or through the channel your organization defined.
What happens next
- The manager decides whether to grant a whole schema, specific tables, or access with protections.
- If approved, the change goes through propagation.
- The request and the decision can be used in future audits.
Common errors
- Requesting access without trying a simple query first.
- Not stating the business purpose.
- Requesting permanent access for a temporary need.
Good practice
- Request access by group when several people need the same thing.
- Use expiry for project or investigation access.
- Ask for masks or filters when you need part of sensitive data.
Next steps
Was this page helpful?
Report a problem on this pageDo not send passwords, keys, tokens, or customer data.