Skip to main content

Common access problems

Learn to recognize access messages, understand why an area or table does not appear, and ask for help with the right information.

When to use this​

  • Use it when you cannot open an area of the Console.
  • Use it when a table does not appear in the Explorer or in the Data Catalog.
  • Use it when a query returns access denied.

Before you start​

  • Note which screen you were on.
  • Note the catalog, schema, and table involved.
  • Confirm whether other people in the same group can reach the same data.

Step by step​

  1. Read the message shown on screen.
  2. Refresh the page if a rule was just created for you.
  3. Check that you are looking in the right catalog.
  4. If the table appears but the query is denied, ask for the data rule to be reviewed.
  5. If the whole area does not appear, ask for your usage role to be reviewed.
  6. Send your administrator the business goal, the data you want, and the deadline you have.

What happens next​

  • The access manager can create or adjust a data rule.
  • The administrator can fix a group, role, or service account.
  • The decision taken is recorded in the audit trail.

Common errors​

  • Confusing seeing metadata with querying data: seeing the table in the catalog does not guarantee you can query it.
  • Requesting broad access with no justification: this usually delays approval.
  • Testing immediately after a change: wait for propagation and try again.

Good practice​

  • Explain the intended use of the data, not just the table's name.
  • Ask for temporary access when the work has a defined deadline.
  • Keep the error message to speed up the investigation.

Next steps​