Hi Francis, I don’t believe that Drill currently has a way to do this: workspaces are global resources shared across all users. The admin (only) can edit all plugin and workspace definitions.
We’d need some form of security tags on each definition, and a way to map users to tags to make this work, but Drill does not yet have this feature. That said, I believe that, while the workspace itself is public, the files in the workspace can be restricted using file permissions when you enable impersonation in Drill. [1] - Paul [1] https://drill.apache.org/docs/securing-drill-introduction/ > On Jul 13, 2017, at 1:09 PM, Francis McGregor-Macdonald <[email protected]> > wrote: > > Hi, > > I have a situation where I would like to restrict access to workspaces > based on the user. I have an instance where I would like to allow some > third-party access to a subset of views. I can't find a standard method > here. > > The only similar issue I could find was this: > https://issues.apache.org/jira/browse/DRILL-3467 > > Is there a standard practice here to limit workspaces for users? > > Thanks, > Francis
