Troubleshooting

As you configure and refine your RBAC setup, you may encounter unexpected behavior that points to a gap in permissions rather than a product defect.

Permission-Related 403 HTTP Errors

Even a well-designed RBAC configuration can produce unexpected behavior if permissions are incomplete. One of the most common issues is a 403 HTTP error that appears when a user attempts an action they appear to have access to. Understanding the root cause can save significant troubleshooting time.

Scenario: Empty Share Report Pane

You have permission to share reports but lack the Read permission for users and groups. When you attempt to share a report, the share pane appears empty, often accompanied by a 403 HTTP error.

Corrective action: Grant the Can Read permission for users and groups to the affected user role.

Note: Similar scenarios occur in other areas where users and groups appear empty. In most cases, the cause is the same — the user lacks read permissions for users and groups.