A Databricks account user who has NOT been added to the workspace is granted CAN EDIT permission on a published dashboard through the Sharing dialog. What is this user's actual effective permission level on the dashboard?
Answer & explanation
Correct answer: C
WHY C: According to Databricks documentation, users who do not have access to the workspace are limited to CAN RUN permissions. Even if CAN EDIT or higher appears in the Sharing dialog, those elevated permissions are not enforced until the user is added to the workspace. If the user is later added, the assigned permission level takes effect. WHY NOT A: The Sharing dialog does display the assigned permission, but it does not override the workspace membership requirement for elevated permissions; the actual effective permission is CAN RUN. WHY NOT B: Non-workspace users are not elevated to CAN MANAGE; they are capped at CAN RUN, the minimum permission tier for dashboard access. WHY NOT D: The Sharing dialog does allow higher permissions to be assigned to non-workspace users, and the assignments are retained; the elevated permissions simply are not enforced until workspace access is granted. WHY NOT E: CAN VIEW is not a distinct permission tier between CAN RUN and CAN EDIT in the dashboard ACL model; the tier applied to non-workspace account users is CAN RUN.